# CVE-2024-39334: Deserialization in n/a

> A deserialization flaw in the MENDELSON AS4 client allows attackers to write files to the victim's computer via malicious XML data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jun 2024
- **Updated:** 13 Nov 2024
- **Also known as:** GHSA-vxf3-94jj-jhmp

## What is CVE-2024-39334?

CVE-2024-39334 is a medium-severity unsafe deserialization vulnerability in n/a, published on 23 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

MENDELSON AS4 before 2024 B376 has a client-side vulnerability when a trading partner provides prepared XML data. When a victim opens the details of this transaction in the client, files can be written to the computer on which the client process is running. (The server process is not affected.)

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2024-39334 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-39334 is a medium-severity unsafe deserialization vulnerability in n/a, published on 23 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-39334 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-39334/ (Markdown: https://insights.sbomify.com/CVE-2024-39334/index.md)
```

## Sources

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

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