# CVE-2024-6441: ORIPA LoaderXML.java deserialization


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Jul 2024
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-j724-5cxg-pq82

## What is CVE-2024-6441?

CVE-2024-6441 is a medium-severity vulnerability in ORIPA, published on 2 Jul 2024. 

### Official description

A vulnerability was found in ORIPA up to 1.72. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file src/main/java/oripa/persistence/doc/loader/LoaderXML.java. The manipulation leads to deserialization. The attack can be launched remotely. Upgrading to version 1.80 is able to address this issue. It is recommended to upgrade the affected component. The identifier VDB-270169 was assigned to this vulnerability.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2024-6441 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6441 is a medium-severity vulnerability in ORIPA, published on 2 Jul 2024. 
Exploitation: There is no known exploitation of CVE-2024-6441 in the wild and no public exploit code.

Affected product: ORIPA. 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-6441/ (Markdown: https://insights.sbomify.com/CVE-2024-6441/index.md)
```

## Sources

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

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