OESA-2024-1135 (CVE-2023-0464)
Vulnerability from osv_openeuler – Published: 2024-02-08 11:06 – Updated: 2026-08-06 11:06 – Source websiteNode.js is an open-source, cross-platform, JavaScript runtime environment, it executes JavaScript code outside of a browser.
Security Fix(es):
A security vulnerability has been identified in all supported versions
of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems.
Policy processing is disabled by default but can be enabled by passing
the -policy' argument to the command line utilities or by calling theX509_VERIFY_PARAM_set1_policies()' function.(CVE-2023-0464)
Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks.
Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether.
Policy processing is disabled by default but can be enabled by passing
the -policy' argument to the command line utilities or by calling theX509_VERIFY_PARAM_set1_policies()' function.(CVE-2023-0465)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"v8-devel-7.8.279.23-1.12.22.11.7.oe2003sp4.aarch64.rpm",
"nodejs-debugsource-12.22.11-7.oe2003sp4.aarch64.rpm",
"nodejs-full-i18n-12.22.11-7.oe2003sp4.aarch64.rpm",
"nodejs-libs-12.22.11-7.oe2003sp4.aarch64.rpm",
"nodejs-12.22.11-7.oe2003sp4.aarch64.rpm",
"nodejs-devel-12.22.11-7.oe2003sp4.aarch64.rpm",
"nodejs-debuginfo-12.22.11-7.oe2003sp4.aarch64.rpm",
"npm-6.14.16-1.12.22.11.7.oe2003sp4.aarch64.rpm"
],
"noarch": [
"nodejs-docs-12.22.11-7.oe2003sp4.noarch.rpm"
],
"src": [
"nodejs-12.22.11-7.oe2003sp4.src.rpm"
],
"x86_64": [
"npm-6.14.16-1.12.22.11.7.oe2003sp4.x86_64.rpm",
"nodejs-devel-12.22.11-7.oe2003sp4.x86_64.rpm",
"nodejs-full-i18n-12.22.11-7.oe2003sp4.x86_64.rpm",
"nodejs-libs-12.22.11-7.oe2003sp4.x86_64.rpm",
"nodejs-debuginfo-12.22.11-7.oe2003sp4.x86_64.rpm",
"nodejs-12.22.11-7.oe2003sp4.x86_64.rpm",
"nodejs-debugsource-12.22.11-7.oe2003sp4.x86_64.rpm",
"v8-devel-7.8.279.23-1.12.22.11.7.oe2003sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "nodejs",
"purl": "pkg:rpm/openEuler/nodejs\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "12.22.11-7.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "Node.js is an open-source, cross-platform, JavaScript runtime environment, it executes JavaScript code outside of a browser.\r\n\r\nSecurity Fix(es):\r\n\r\nA security vulnerability has been identified in all supported versions\r\n\r\nof OpenSSL related to the verification of X.509 certificate chains\nthat include policy constraints. Attackers may be able to exploit this\nvulnerability by creating a malicious certificate chain that triggers\nexponential use of computational resources, leading to a denial-of-service\n(DoS) attack on affected systems.\r\n\r\nPolicy processing is disabled by default but can be enabled by passing\nthe `-policy\u0026apos; argument to the command line utilities or by calling the\n`X509_VERIFY_PARAM_set1_policies()\u0026apos; function.(CVE-2023-0464)\r\n\r\nApplications that use a non-default option when verifying certificates may be\nvulnerable to an attack from a malicious CA to circumvent certain checks.\r\n\r\nInvalid certificate policies in leaf certificates are silently ignored by\nOpenSSL and other certificate policy checks are skipped for that certificate.\nA malicious CA could use this to deliberately assert invalid certificate policies\nin order to circumvent policy checking on the certificate altogether.\r\n\r\nPolicy processing is disabled by default but can be enabled by passing\nthe `-policy\u0026apos; argument to the command line utilities or by calling the\n`X509_VERIFY_PARAM_set1_policies()\u0026apos; function.(CVE-2023-0465)",
"id": "OESA-2024-1135",
"modified": "2026-08-06T11:06:35Z",
"published": "2024-02-08T11:06:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1135"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-0464"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-0465"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "nodejs security update",
"upstream": [
"CVE-2023-0464",
"CVE-2023-0465"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.