ePA 3.x Integration: TLS Certificate Verification Universally Disabled
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| fbeta-GmbH | ePA3-Service-OpenSource | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Fbeta-gmbh | Epa3-service-opensource |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.310% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Fbeta-gmbh
Fbeta-gmbh epa3-service-opensource |
|
| Vendors & Products |
Fbeta-gmbh
Fbeta-gmbh epa3-service-opensource |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | ePA 3.x Integration: TLS Certificate Verification Universally Disabled | |
| Weaknesses | CWE-295 | |
| References |
|
|
| Metrics |
cvssV3_1
|