dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-39334

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

MENDELSON AS4 client versions before 2024 B376 contain a client-side file write vulnerability. When a trading partner submits crafted XML data and the victim opens the transaction details in the AS4 client interface, the client can be tricked into writing arbitrary files to the local filesystem where the client process runs. This appears to be a client-side injection issue (likely XML-related) that allows path traversal or file creation via malicious XML payloads.

MitigationUpdate MENDELSON AS4 to version 2024 B376 or later. Until patched, users should avoid opening transaction details from untrusted trading partners, and administrators should implement network segmentation to limit client exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MENDELSON AS4 client installation
    Check for the MENDELSON AS4 client application in your installed programs list, or look for the client process running (typically named 'as4client.exe' or similar in Task Manager). Also check the installation directory, commonly under C:\Program Files\MENDELSON or C:\Program Files (x86)\MENDELSON.
    Affected if The MENDELSON AS4 client is installed and running on the system.
  2. Identify installed version
    Open the AS4 client application and navigate to Help > About, or right-click the executable and select Properties > Details to view the version information. Compare the version number to the 2024 B376 release.
    Affected if The installed version is earlier than 2024 B376.
  3. Verify client interface access
    Confirm the AS4 client GUI is accessible and the transaction viewing feature is available. This feature allows users to view details of received transactions from trading partners.
    Affected if The AS4 client interface with transaction detail viewing is enabled and accessible.
  4. Assess trading partner exposure
    Review the configured trading partners in the AS4 client. Check if any trading partners are marked as untrusted or external, or if the client accepts connections from partners outside your organization.
    Affected if The client is configured to receive or display transactions from untrusted or external trading partners.

You are affected if the MENDELSON AS4 client version is installed and is earlier than 2024 B376, and the client is used to view transaction details from trading partners.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update MENDELSON AS4 to version 2024 B376 or later. Until patched, users should avoid opening transaction details from untrusted trading partners, and administrators should implement network segmentation to limit client exposure.

Recommended fix Moderate confidence

2024 B376 or later

  1. Identify the currently installed MENDELSON AS4 client version
  2. Verify the installed version is earlier than 2024 B376
  3. Obtain the MENDELSON AS4 version 2024 B376 or later from the vendor
  4. Back up the current MENDELSON AS4 client configuration and data
  5. Stop the MENDELSON AS4 client application
  6. Install version 2024 B376 or later
  7. Verify the installation was successful
  8. Restart the MENDELSON AS4 client

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39334 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-39334 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data