121 lines
4.9 KiB
JSON
121 lines
4.9 KiB
JSON
{
|
|
"dataType": "CVE_RECORD",
|
|
"cveMetadata": {
|
|
"state": "PUBLISHED",
|
|
"cveId": "CVE-2025-62819",
|
|
"assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
|
|
"assignerShortName": "mitre",
|
|
"dateUpdated": "2026-11-06T19:15:53.709Z",
|
|
"dateReserved": "2025-10-23T00:00:00.000Z",
|
|
"datePublished": "2026-11-02T00:00:00.000Z"
|
|
},
|
|
"containers": {
|
|
"cna": {
|
|
"providerMetadata": {
|
|
"orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
|
|
"shortName": "mitre",
|
|
"dateUpdated": "2026-11-02T14:35:31.782Z"
|
|
},
|
|
"descriptions": [
|
|
{
|
|
"lang": "en",
|
|
"value": "Keyfactor EJBCA through 9.3.3 performs insufficient authorization checks when self-renewing a client certificate via the RA (Registration Authority) User Interface. This allows a remote user, authenticated with a valid client certificate, to renew their certificate even if the end entity status and/or profile settings should deny renewal. The attacker must have a valid TLS client certificate, and must be authorized to use the RA User Interface, either with the certificate, or via a role membership for PublicAccessAuthenticationToken."
|
|
}
|
|
],
|
|
"affected": [
|
|
{
|
|
"vendor": "n/a",
|
|
"product": "n/a",
|
|
"versions": [
|
|
{
|
|
"version": "n/a",
|
|
"status": "affected"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"references": [
|
|
{
|
|
"url": "https://trust.keyfactor.com"
|
|
},
|
|
{
|
|
"url": "https://support.keyfactor.com/hc/en-us/articles/57971026069531-Security-advisory-EJBCA-unauthorized-client-certificate-renewal-in-RA-Web"
|
|
}
|
|
],
|
|
"problemTypes": [
|
|
{
|
|
"descriptions": [
|
|
{
|
|
"type": "text",
|
|
"lang": "en",
|
|
"description": "n/a"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
},
|
|
"adp": [
|
|
{
|
|
"problemTypes": [
|
|
{
|
|
"descriptions": [
|
|
{
|
|
"type": "CWE",
|
|
"cweId": "CWE-862",
|
|
"lang": "en",
|
|
"description": "CWE-862 Missing Authorization"
|
|
}
|
|
]
|
|
}
|
|
],
|
|
"metrics": [
|
|
{
|
|
"cvssV3_1": {
|
|
"scope": "UNCHANGED",
|
|
"version": "3.1",
|
|
"baseScore": 6.5,
|
|
"attackVector": "NETWORK",
|
|
"baseSeverity": "MEDIUM",
|
|
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
|
|
"integrityImpact": "HIGH",
|
|
"userInteraction": "NONE",
|
|
"attackComplexity": "LOW",
|
|
"availabilityImpact": "NONE",
|
|
"privilegesRequired": "LOW",
|
|
"confidentialityImpact": "NONE"
|
|
}
|
|
},
|
|
{
|
|
"other": {
|
|
"type": "ssvc",
|
|
"content": {
|
|
"timestamp": "2026-11-06T19:15:49.175626Z",
|
|
"id": "CVE-2025-62819",
|
|
"options": [
|
|
{
|
|
"Exploitation": "none"
|
|
},
|
|
{
|
|
"Automatable": "no"
|
|
},
|
|
{
|
|
"Technical Impact": "partial"
|
|
}
|
|
],
|
|
"role": "CISA Coordinator",
|
|
"version": "2.0.3"
|
|
}
|
|
}
|
|
}
|
|
],
|
|
"title": "CISA ADP Vulnrichment",
|
|
"providerMetadata": {
|
|
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
|
|
"shortName": "CISA-ADP",
|
|
"dateUpdated": "2026-11-06T19:15:53.709Z"
|
|
}
|
|
}
|
|
]
|
|
},
|
|
"dataVersion": "5.2"
|
|
} |