dbcve.org
XML External Entity (XXE)Weakness · CWE-611

CVE-2024-54005

MEDIUM · 5.1 CVSS v3.1 Published 2024-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
No privileges Zero-click

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
A vulnerability has been identified in COMOS V10.3 (All versions < V10.3.3.5.8), COMOS V10.4.0 (All versions), COMOS V10.4.1 (All versions), COMOS V10.4.2 (All versions), COMOS V10.4.3 (All versions < V10.4.3.0.47), COMOS V10.4.4 (All versions < V10.4.4.2), COMOS V10.4.4.1 (All versions < V10.4.4.1.21). The PDMS/E3D Engineering Interface improperly handles XML External Entity (XXE) entries when communicating with an external application. This could allow an attacker to extract any file with a known location on the user's system or accessible network folders by injecting malicious data into the communication channel between the two systems.

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 · high confidence

This is an XXE (XML External Entity) injection vulnerability in COMOS PDMS/E3D Engineering Interface. The software improperly handles XML External Entity entries when communicating with external applications, allowing attackers to inject malicious XML that references external entities to extract sensitive files from the user's local system or accessible network folders.

MitigationUpdate COMOS to the patched versions (V10.3.3.5.8, V10.4.3.0.47, V10.4.4.2, or V10.4.4.1.21) and ensure XML parsers are configured to disable external entity and DTD processing.

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
Local
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/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. Identify COMOS version
    Locate the COMOS installation directory (typically C:\Program Files\COMOS or C:\Program Files (x86)\COMOS) and check the version information in the program's about dialog, or right-click the main COMOS executable and view Properties > Details for the File Version.
    Affected if The installed version is older than V10.3.3.5.8, V10.4.3.0.47, V10.4.4.2, or V10.4.4.1.21 (versions prior to these patched releases are vulnerable)
  2. Verify Engineering Interface is active
    Check if the PDMS/E3D Engineering Interface module is enabled in COMOS. This is typically configured in COMOS administration tools or within the project's system settings under the interface or integration configuration area.
    Affected if The Engineering Interface module is enabled and configured to exchange data with external applications via XML
  3. Inspect XML parser security configuration
    Examine COMOS configuration files or settings related to XML parsing. Look for XML parser settings in COMOS configuration files, registry, or the Engineering Interface settings that control external entity resolution and DTD processing.
    Affected if External entity resolution and DTD processing are not explicitly disabled in the XML parser configuration used by the Engineering Interface

A system is affected if it runs a COMOS version prior to the patched releases and has the Engineering Interface enabled with XML processing that allows external entity resolution.

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 COMOS to the patched versions (V10.3.3.5.8, V10.4.3.0.47, V10.4.4.2, or V10.4.4.1.21) and ensure XML parsers are configured to disable external entity and DTD processing.

Recommended fix Moderate confidence

COMOS V10.3.3.5.8, V10.4.3.0.47, V10.4.4.2, or V10.4.4.1.21 depending on your current branch

  1. Upgrade COMOS V10.3 to version V10.3.3.5.8 or later
  2. Upgrade COMOS V10.4.3 to version V10.4.3.0.47 or later
  3. Upgrade COMOS V10.4.4 to version V10.4.4.2 or later
  4. Upgrade COMOS V10.4.4.1 to version V10.4.4.1.21 or later
  5. For COMOS V10.4.0, V10.4.1, and V10.4.2 (all versions), upgrade to the next available newer branch (V10.4.3 or later)

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-54005 — 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-54005 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