Security readout for executives and security teams
Plain-English summary
CVE-2024-23079 reports a possible crash condition in JGraphT Core 1.5.2 caused by a NullPointerException in ToleranceDoubleComparator.compare. The record is explicitly disputed, with third parties saying there is not reasonable evidence that this is a real vulnerability. Treat it as a low-confidence availability concern, not confirmed compromise risk.
Executive priority
Handle through normal vulnerability management, not emergency response. The main business risk is potential application disruption in affected Java applications, but the evidence is disputed and there is no cited active exploitation.
Technical view
The CVE describes a NullPointerException in org.jgrapht.alg.util.ToleranceDoubleComparator::compare(Double, Double), with CVSS 3.1 score 6.2 and vector AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. The stated impact is availability only. The CVE also notes the report may be tool-generated and insufficiently supported.
Likely exposure
Exposure is likely limited to applications that include JGraphT Core 1.5.2 and use the affected comparator path with inputs that can trigger a null-handling failure. The CVE affected-product metadata is incomplete, so dependency inventory is required.
Exploitation context
No CISA KEV listing is provided, and the supplied sources do not show active exploitation. The CVSS vector is local, availability-only, and requires reaching vulnerable application logic. The vulnerability status is disputed, so exploitation assumptions should be cautious.
Researcher notes
The record’s CWE-120 classification appears unusual for a Java NullPointerException, and affected CPE data is not populated. Researchers should verify reproducibility against JGraphT Core 1.5.2 and distinguish library behavior from application misuse before treating this as a confirmed vulnerability.
Mitigation direction
- Inventory applications using JGraphT Core 1.5.2.
- Check JGraphT project guidance, issues, and releases for vendor-confirmed action.
- Upgrade only according to validated vendor or maintainer guidance.
- Add application-level null validation where untrusted data reaches graph comparison logic.
- Prioritize regression testing before dependency changes.
Validation and detection
- Review dependency manifests for org.jgrapht:jgrapht-core version 1.5.2.
- Identify code paths using ToleranceDoubleComparator or related algorithms.
- Confirm whether nullable values can reach those paths.
- Check application logs for recurring NullPointerException in this component.
- Track CVE updates because the record is disputed.
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-120: 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-23079 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
- Medium
- CVSS
- 6.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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
1 official scoreWe 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:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.53.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.2MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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
- https://github.com/jgrapht/jgraphtCVE reference, mitre
- https://gist.github.com/LLM4IG/c19779800945cd0a400d2150fb83d079CVE reference, mitre
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.
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.