CVE-2022-34831

{"id": "CVE-2022-34831", "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 3.9}]}, "published": "2022-09-14T03:15:08.050", "references": [{"url": "https://support.keyfactor.com/s/detail/a6x1Q000000CwC5QAK", "tags": ["Vendor Advisory"], "source": "cve@mitre.org"}, {"url": "https://www.primekey.com/products/ejbca-enterprise/", "tags": ["Product", "Vendor Advisory"], "source": "cve@mitre.org"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-295"}]}], "descriptions": [{"lang": "en", "value": "An issue was discovered in Keyfactor PrimeKey EJBCA before 7.9.0, related to possible inconsistencies in DNS identifiers submitted in an ACME order and the corresponding CSR submitted during finalization. During the ACME enrollment process, an order is submitted containing an identifier for one or multiple dnsNames. These are validated properly in the ACME challenge. However, if the validation passes, a non-compliant client can include additional dnsNames the CSR sent to the finalize endpoint, resulting in EJBCA issuing a certificate including the identifiers that were not validated. This occurs even if the certificate profile is configured to not allow a DN override by the CSR."}, {"lang": "es", "value": "Se ha detectado un problema en Keyfactor PrimeKey EJBCA versiones anteriores a 7.9.0, relacionado con posibles incoherencias en los identificadores DNS enviados en un pedido ACME y el correspondiente CSR enviado durante la finalizaci\u00f3n. Durante el proceso de inscripci\u00f3n en ACME, es enviada una orden que contiene un identificador para uno o varios dnsNames. Estos son comprobados apropiadamente en la impugnaci\u00f3n de ACME. Sin embargo, si la comprobaci\u00f3n es superada, un cliente no conforme puede incluir dnsNames adicionales en la CSR enviada al endpoint de finalizaci\u00f3n, resultando en que EJBCA emita un certificado que incluya los identificadores que no fueron comprobados. Esto ocurre incluso si el perfil de certificado est\u00e1 configurado para no permitir una anulaci\u00f3n de DN por el CSR"}], "lastModified": "2022-09-16T19:18:27.957", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:primekey:ejbca:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "1C4A9E1E-3709-4B52-AE01-A8556FED5660", "versionEndExcluding": "7.9.0"}], "operator": "OR"}]}], "sourceIdentifier": "cve@mitre.org"}