Security readout for executives and security teams
Plain-English summary
Nokogiri releases before 1.16.5 bundled a libxml2 version containing a critical-rated flaw in the separate xmllint utility. Nokogiri’s maintainers state that Nokogiri neither provides nor exposes xmllint, so normal Nokogiri users are not affected. The dependency should still be updated for hygiene and scanner compliance.
Executive priority
Treat this as a routine dependency update, not a critical incident, unless xmllint is independently installed or exposed. Confirm inventory and upgrade during the next appropriate maintenance window. Escalate only if validation reveals a separate vulnerable libxml2 deployment with an accessible xmllint tool.
Technical view
Nokogiri before 1.16.5 bundled libxml2 2.12.6, affected by CVE-2024-34459 and associated with CWE-427. Version 1.16.5 updates bundled libxml2 to 2.12.7. Although the supplied CVSS 4.0 score is 9.3, the vulnerable xmllint tool is outside Nokogiri’s exposed functionality, materially limiting product-level risk.
Likely exposure
Exposure through Nokogiri itself is unlikely because the affected xmllint utility is not shipped or exposed by Nokogiri. Investigate separately if systems install or invoke xmllint from another libxml2 package or distribution source; the supplied evidence does not establish that scenario as part of Nokogiri.
Exploitation context
The source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation. The high CVSS score describes the underlying libxml2 issue, but maintainers report no exploitable path through Nokogiri because xmllint is unavailable there.
Researcher notes
The key distinction is component presence versus reachable functionality. The bundled libxml2 version carries the underlying issue, but Nokogiri does not expose the affected xmllint executable. Validate actual artifacts and independent system packages before suppressing findings. The supplied sources establish the dependency update and maintainer assessment, but not active exploitation.
Mitigation direction
- Upgrade Nokogiri to version 1.16.5 or later through normal dependency management.
- Rebuild deployment artifacts so bundled libxml2 2.12.7 or later is present.
- Review vendor guidance if xmllint is installed independently from another package source.
- Prioritize internet-facing systems only if validation finds a separately exposed xmllint installation.
Validation and detection
- Inventory applications and lockfiles for Nokogiri versions earlier than 1.16.5.
- Confirm deployed artifacts use Nokogiri 1.16.5 or later.
- Determine whether xmllint exists independently and identify its supplying libxml2 package.
- Document scanner findings as non-exploitable through Nokogiri when the maintainer conditions apply.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-427: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-58377 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:N1.80VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
0NoneVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-r95h-9x8f-r3f7)CVE reference, VulnCheck · vendor-advisory
- Patch CommitCVE reference, VulnCheck · patch
- VulnCheck Advisory: Nokogiri before 1.16.5 libxml2 Dependency UpdateCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Uncontrolled Search Path Element
Uncontrolled Search Path Element represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.