# CVE-2024-23082: Integer overflow in n/a

> Disputed integer overflow in ThreeTen Backport DateTimeFormatter parsing may cause denial of service, though evidence is contested.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-rgx7-8wqv-m224

## What is CVE-2024-23082?

CVE-2024-23082 is a vulnerability in n/a, published on 8 Apr 2024. 

### Official description

ThreeTen Backport v1.6.8 was discovered to contain an integer overflow via the component org.threeten.bp.format.DateTimeFormatter::parse(CharSequence, ParsePosition). 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.

## Which versions are affected by CVE-2024-23082?


## How do I fix CVE-2024-23082?

No fix has been published for CVE-2024-23082 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-23082 being exploited?

There is no known exploitation of CVE-2024-23082 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23082 and fix it if it is affected.

What it is: CVE-2024-23082 is a vulnerability in n/a, published on 8 Apr 2024. 
Exploitation: There is no known exploitation of CVE-2024-23082 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-23082/ (Markdown: https://insights.sbomify.com/CVE-2024-23082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-23082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-23082
- OSV: https://osv.dev/vulnerability/CVE-2024-23082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-23082/
Summaries are generated and may contain mistakes; the official description above is the record.