CyberRota Analysis
AI-GeneratedThe ePA 3.x Integration in affected versions of Exchange is vulnerable due to the disabling of TLS certificate verification, allowing a network-positioned attacker to intercept and manipulate ePA traffic by presenting arbitrary certificates. This vulnerability poses a significant risk to the confidentiality and integrity of medical information exchanged within Germany's electronic patient record system. Organizations utilizing ePA 3.x Integration should prioritize upgrading to version 1.3.0 to mitigate this high-severity threat.
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 disables TLS certificate verification for both ePA connections in app/vau/VAUProtokoll.py and Konnektor connections in app/konnektor/Konnektor.py. A network-positioned attacker can present an arbitrary certificate, terminate the TLS connection, and intercept ePA traffic. The VAU protocol does not provide an effective fallback because its application-layer certificate validation is also broken in affected versions. The Konnektor session uses self.session.verify set to False while the client authenticates with self.session.cert, so an attacker impersonating the Konnektor can receive the client's mutual TLS certificate exchange and observe smartcard operations. This issue is fixed in version 1.3.0.