CyberRota Analysis
AI-GeneratedThe ePA 3.x Integration prior to version 1.3.0 is vulnerable due to improper handling of the request counter, which allows attackers to reuse AES-GCM nonce and key combinations, potentially exposing sensitive patient health records and enabling the injection of malicious responses. Organizations utilizing this integration should prioritize updating to version 1.3.0 to mitigate risks associated with data exposure and message forgery. This vulnerability is particularly critical for healthcare providers and entities handling electronic patient records in Germany.
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 leaves request_counter unchanged in app/vau/VAUProtokoll.py while constructing VAU messages. The frozen client request counter causes the server side to reuse AES-GCM nonce and key combinations across responses. A network attacker who collects repeated ciphertexts can recover the XOR of plaintexts and use predictable inner HTTP headers and JSON fields to recover sensitive data, including patient health records. Repeated nonces can also enable recovery of the GHASH authentication key through the Joux forbidden attack, allowing forged AES-GCM messages and injection of malicious responses. The response-counter check also fails to maintain last_response_counter, weakening replay and ordering validation. This issue is fixed in version 1.3.0.