CyberRota Analysis
AI-GeneratedThe ePA 3.x Integration prior to version 1.3.0 is vulnerable due to improper validation of VAU server certificates, allowing a network-positioned attacker to intercept and manipulate encrypted VAU traffic. This critical flaw enables the attacker to impersonate the VAU server, compromising the confidentiality and integrity of sensitive medical information exchanged between the DiGA backend and the ePA system. Organizations utilizing this integration should prioritize immediate updates to version 1.3.0 to mitigate the risk of exploitation.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
ePA 3.x Integration implements the authorization workflow and writes Medical Information Objects to Germany's electronic patient record. Prior to 1.3.0, ePA 3.x Integration performs VAU server certificate validation in app/vau/VAUProtokoll.py without anchoring the signed_vau_server_pub_keys and AUT_VAU_CertData certificate path to independent trusted material. A network-positioned attacker between the DiGA backend and the ePA system can intercept the VAU handshake, supply attacker-controlled certificate and key material, and satisfy the circular trust relationship. Because TLS certificate verification is also disabled in affected versions, no independent server-authentication layer prevents the attack. The attacker can impersonate the VAU server, control the negotiated session keys, and read or modify all encrypted VAU traffic. This issue is fixed in version 1.3.0.