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

CVE-2024-49704

MEDIUM · 5.5 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 →
58/100
Remediation priority · Elevated
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
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 Generic Data Mapper, the Engineering Adapter, and the Engineering Interface improperly handle XML External Entity (XXE) entries when parsing configuration and mapping files. This could allow an attacker to extract any file with a known location on the user's system or accessible network folders by persuading a user to use a maliciously crafted configuration or mapping file in one of the affected components.

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 where the Generic Data Mapper, Engineering Adapter, and Engineering Interface improperly handle XXE entries when parsing XML configuration and mapping files. An attacker can craft malicious XML files that reference external entities to extract sensitive files from the local system or accessible network folders.

MitigationOrganizations should update to the patched versions (V10.3.3.5.8+, V10.4.3.0.47+, V10.4.4.2+, V10.4.4.1.21+) and instruct users to avoid opening untrusted configuration or mapping files from unknown sources.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Locate COMOS installation and version
    Check the Windows registry for COMOS installation under HKLM\SOFTWARE\Wow6432Node\COMOS or look for COMOS installation directories (commonly C:\Program Files\COMOS or C:\COMOS). Locate the COMOS version information in the About dialog or installation directories.
    Affected if COMOS version is lower than V10.3.3.5.8, V10.4.3.0.47, V10.4.4.2, or V10.4.4.1.21 and the product is installed.
  2. Identify if Generic Data Mapper is enabled
    Check COMOS configuration files (typically XML files in the COMOS working directory or project folder) for references to 'GenericDataMapper' or 'GDM' module. Look in project configuration XML files or COMOS system settings.
    Affected if Generic Data Mapper component is configured and COMOS version is unpatched.
  3. Identify if Engineering Adapter is enabled
    Search COMOS configuration for 'EngineeringAdapter' or 'EA' module references in XML configuration files within the COMOS system directory or project settings.
    Affected if Engineering Adapter component is configured and COMOS version is unpatched.
  4. Identify if Engineering Interface is enabled
    Search COMOS configuration for 'EngineeringInterface' or 'EI' module references in XML configuration files or check if import/export profiles are defined in the COMOS system.
    Affected if Engineering Interface component is configured and COMOS version is unpatched.
  5. Review XML configuration and mapping files
    Examine XML configuration files in the COMOS project directory, especially files under folders named 'Configuration', 'Mapping', 'Import', or 'Export'. Check for any custom or imported XML files that may contain untrusted content.
    Affected if Custom or imported XML configuration/mapping files exist in the COMOS environment and the version is unpatched.

A user is affected if they have a COMOS version lower than the fixed releases (V10.3.3.5.8, V10.4.3.0.47, V10.4.4.2, or V10.4.4.1.21) and have the Generic Data Mapper, Engineering Adapter, or Engineering Interface components enabled with access to parse XML configuration files.

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

Organizations should update to the patched versions (V10.3.3.5.8+, V10.4.3.0.47+, V10.4.4.2+, V10.4.4.1.21+) and instruct users to avoid opening untrusted configuration or mapping files from unknown sources.

Recommended fix High confidence

COMOS V10.3.x -> V10.3.3.5.8+; COMOS V10.4.3.x -> V10.4.3.0.47+; COMOS V10.4.4.x -> V10.4.4.2+; COMOS V10.4.4.1.x -> V10.4.4.1.21+; COMOS V10.4.0/10.4.1/10.4.2 -> V10.4.3.0.47+ or V10.4.4.2+

  1. 1. Identify the currently installed COMOS version by checking the product's 'About' information or system properties.
  2. 2. For COMOS V10.3.x users: Upgrade to version V10.3.3.5.8 or later.
  3. 3. For COMOS V10.4.3.x users: Upgrade to version V10.4.3.0.47 or later.
  4. 4. For COMOS V10.4.4.x users: Upgrade to version V10.4.4.2 or later.
  5. 5. For COMOS V10.4.4.1.x users: Upgrade to version V10.4.4.1.21 or later.
  6. 6. For COMOS V10.4.0, V10.4.1, and V10.4.2 (all versions): These version branches have no fix indicated in the advisory; upgrade to a later fixed branch (V10.4.3.0.47 or higher, or V10.4.4.2 or higher).
  7. 7. After upgrading, validate that the Generic Data Mapper, Engineering Adapter, and Engineering Interface components function correctly with existing configuration and mapping files.
Caveat Review release notes for compatibility notes when upgrading across minor version branches (e.g., from V10.4.0-V10.4.2 to V10.4.3 or V10.4.4)

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49704 — 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-49704 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