CVE-2024-23086: Apfloat v1.10.1 was discovered to contain a stack overflow via the component org.apfloat.internal.DoubleMod...
Apfloat v1.10.1 was discovered to contain a stack overflow via the component org.apfloat.internal.DoubleModMath::modPow(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
CVE-2024-23086 claims Apfloat v1.10.1 has a stack overflow in a math component. The CVE record itself says the finding is disputed by multiple third parties and may be based on unreliable tooling. Treat this as an item to verify, not as confirmed critical exposure.
Executive priority
Medium monitoring priority unless Apfloat v1.10.1 is confirmed in business-critical or internet-facing systems. The headline score is critical, but the evidence is disputed and no exploitation is cited.
Technical view
The reported issue concerns org.apfloat.internal.DoubleModMath::modPow(double) in Apfloat v1.10.1. The record assigns CVSS 9.8 and CWE-125, but affected vendor/product data is listed as n/a. The CVE description includes an explicit dispute over whether sufficient evidence exists to confirm a vulnerability.
Likely exposure
Organizations may be exposed only if they use Apfloat v1.10.1 or software that bundles it. The provided sources do not identify affected CPEs, downstream products, reachable attack surfaces, or fixed versions.
Exploitation context
No KEV listing is present, and the provided sources do not show active exploitation. The reported network, unauthenticated CVSS vector should not be treated as confirmed exploitability because the vulnerability itself is disputed.
Researcher notes
The CVE has unusual signals: n/a affected product metadata, CWE-125 while the description says stack overflow, and an explicit dispute statement. Validate dependency presence and code reachability before escalating. Do not assume the linked gist proves exploitability without independent confirmation.
Mitigation direction
Inventory applications and dependencies for Apfloat v1.10.1 usage.
Review the upstream Apfloat repository and CVE record for clarification or fixes.
Avoid making risk decisions from the CVSS score alone due to the dispute.
If Apfloat is used in exposed services, prioritize code-owner review of reachable inputs.
Validation and detection
Check software bills of materials for Apfloat v1.10.1.
Confirm whether org.apfloat.internal.DoubleModMath is present in deployed builds.
Ask application owners whether untrusted input can reach Apfloat calculations.
Track CVE updates for changes to dispute status, affected versions, or remediation.
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-125: 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.
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-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.