Files
vuln-cve/data/2026/45xxx/CVE-2026-45575.json
T

135 lines
5.4 KiB
JSON

{
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"cveMetadata": {
"cveId": "CVE-2026-45575",
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"state": "PUBLISHED",
"assignerShortName": "GitHub_M",
"dateReserved": "2026-05-12T19:00:14.600Z",
"datePublished": "2026-05-26T21:01:51.745Z",
"dateUpdated": "2026-05-28T14:11:30.565Z"
},
"containers": {
"cna": {
"title": "epa4all-client: Improper Verification of Cryptographic Signature",
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-347",
"lang": "en",
"description": "CWE-347: Improper Verification of Cryptographic Signature",
"type": "CWE"
}
]
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.4,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
}
}
],
"references": [
{
"name": "https://github.com/oviva-ag/epa4all-client/security/advisories/GHSA-gqx7-6552-67hf",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/oviva-ag/epa4all-client/security/advisories/GHSA-gqx7-6552-67hf"
},
{
"name": "https://github.com/oviva-ag/epa4all-client/pull/36",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/oviva-ag/epa4all-client/pull/36"
}
],
"affected": [
{
"vendor": "oviva-ag",
"product": "epa4all-client",
"versions": [
{
"version": "< 1.2.2",
"status": "affected"
}
]
},
{
"vendor": "com.oviva.telematik",
"product": "epa4all-client",
"versions": [
{
"version": "< 1.2.2",
"status": "affected"
}
]
}
],
"providerMetadata": {
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M",
"dateUpdated": "2026-05-26T21:01:51.745Z"
},
"descriptions": [
{
"lang": "en",
"value": "epa4all-client is the Java Client for epa4all / ePA 3.0 in the Telematik Infrastruktur. Prior to 1.2.2, an attacker who can MITM the TLS connection between the client and the IDP (within the TI network) can substitute a forged discovery document. The forged document redirects uri_puk_idp_enc and uri_puk_idp_sig to attacker-controlled URLs. The client then encrypts the SMC-B-signed challenge response to the attacker's encryption key and POSTs it to the attacker's auth endpoint. This captures the signed authentication material. This vulnerability is fixed in 1.2.2."
}
],
"source": {
"advisory": "GHSA-gqx7-6552-67hf",
"discovery": "UNKNOWN"
}
},
"adp": [
{
"metrics": [
{
"other": {
"type": "ssvc",
"content": {
"timestamp": "2026-05-28T14:11:18.105155Z",
"id": "CVE-2026-45575",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"version": "2.0.3"
}
}
}
],
"title": "CISA ADP Vulnrichment",
"providerMetadata": {
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP",
"dateUpdated": "2026-05-28T14:11:30.565Z"
}
}
]
}
}