# CVE-2025-24336: Denial of service in SXF Common Library

> Attackers can crash products using the SXF Common Library by providing crafted input files, causing a denial of service.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Jan 2025
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-cg49-m89q-2j7q

## What is CVE-2025-24336?

CVE-2025-24336 is a low-severity denial of service vulnerability in General Incorporated Association OCF SXF Common Library, published on 31 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

SXF Common Library handles input data improperly. If a product using the library reads a crafted file, the product may be crashed.

Weakness: CWE-237 (Improper Handling of Structural Elements)

## Which versions are affected by CVE-2025-24336?


## How do I fix CVE-2025-24336?

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

## Is CVE-2025-24336 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24336 and fix it if it is affected.

What it is: CVE-2025-24336 is a low-severity denial of service vulnerability in General Incorporated Association OCF SXF Common Library, published on 31 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-24336 in the wild and no public exploit code.

Affected product: General Incorporated Association OCF SXF Common Library. 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-2025-24336/ (Markdown: https://insights.sbomify.com/CVE-2025-24336/index.md)
```

## Sources

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

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