CVE-2024-23078: JGraphT Core v1.5.2 was discovered to contain a NullPointerException via the component org.jgrapht.alg.util...
JGraphT Core v1.5.2 was discovered to contain a NullPointerException via the component org.jgrapht.alg.util.ToleranceDoubleComparator::compare(Double, Double). NOTE: this is disputed by multiple third parties who believe there was not reasonable evidence to determine the existence of a vulnerability. The submission may have been based on a tool that is not sufficiently robust for vulnerability identification.
Security readout for executives and security teams
Plain-English summary
This CVE claims JGraphT Core 1.5.2 can trigger a NullPointerException in a comparator method. The record itself notes the vulnerability is disputed by multiple third parties, citing insufficient evidence. Treat this as a dependency triage item, not a confirmed emergency, unless your application exposes the affected code path to untrusted input.
Executive priority
Medium for triage; lower for emergency response. The score is critical, but the vulnerability is disputed, affected product data is incomplete, and no active exploitation is cited. Prioritize inventory and exposure validation before allocating major remediation effort.
Technical view
The reported issue is CWE-476 in org.jgrapht.alg.util.ToleranceDoubleComparator::compare(Double, Double). The CVSS vector is listed as 9.1, network exploitable, unauthenticated, with high confidentiality and availability impact. However, the CVE description flags the report as disputed and possibly based on weak automated tooling evidence.
Likely exposure
Potentially relevant only to applications using JGraphT Core v1.5.2 and reaching this comparator through attacker-influenced data. The CVE record lists affected vendor/product as n/a, so exposure boundaries are not well established from the provided sources.
Exploitation context
No CISA KEV listing is provided, and the sources do not show active exploitation. The public reference includes a GitHub project page and a gist, but the CVE text emphasizes that the finding is disputed and evidence may be insufficient.
Researcher notes
Key uncertainty is validity. The CVE asserts a NullPointerException but explicitly says multiple third parties dispute whether enough evidence exists to call it a vulnerability. Research should focus on reachability, attacker control, impact beyond ordinary exception behavior, and any upstream maintainer position.
Mitigation direction
Inventory applications and libraries for JGraphT Core v1.5.2.
Check JGraphT project guidance, releases, and issues for any official clarification.
Validate or reject null Double inputs before comparator use where applicable.
Limit attacker-controlled data from reaching graph comparison logic.
Track the CVE record for updates because the finding is disputed.
Validation and detection
Confirm whether JGraphT Core v1.5.2 exists in dependency manifests or SBOMs.
Search internal code for ToleranceDoubleComparator usage.
Review whether external input can influence values passed to compare.
Test null-handling behavior in non-production if the code path is reachable.
Document rationale if the disputed CVE is accepted as not applicable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-476: 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.
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.
1CVSS vectors
3Timeline events
2ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.