dbcve.org
ComosApplication · Siemens

CVE-2023-43503

HIGH · 7.5 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 10.4.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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 (All versions < V10.4.4). Caching system in the affected application leaks sensitive information such as user and project information in cleartext via UDP.

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

The COMOS application's caching system transmits sensitive user and project information in unencrypted cleartext over the UDP protocol, allowing network-adjacent attackers to intercept this sensitive data via packet capture.

MitigationUpgrade COMOS to version V10.4.4 or later to obtain the patch; alternatively, implement network segmentation and firewall rules to restrict UDP access from untrusted networks.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ComosApplication
Affected:< 10.4.4

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/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 installation and version
    Locate the COMOS installation directory and check the version information, typically found in the application's about dialog, installation logs, or version file within the program folder
    Affected if The installed version is any version prior to 10.4.4 (e.g., 10.4.3, 10.4.2, 10.3.x, etc.)
  2. Determine if COMOS caching system is in use
    Check the COMOS configuration files or application settings to verify if the caching system feature is enabled. This may be visible in the COMOS administration console or configuration panel
    Affected if The caching system is enabled and configured to run
  3. Verify UDP network exposure
    Use network monitoring tools (such as netstat, Wireshark, or similar) to observe outbound or inbound UDP traffic originating from the COMOS application or associated services
    Affected if UDP traffic is detected on ports used by the COMOS caching system and the network is accessible to untrusted adjacent attackers
  4. Inspect caching traffic for cleartext content
    Capture UDP packets using a packet sniffer on the network segment where COMOS communicates, then analyze the payload to determine if sensitive user credentials, project data, or other confidential information is transmitted in cleartext
    Affected if Packet capture reveals sensitive user or project information in unencrypted plain text within UDP datagrams

You are affected if COMOS version is below 10.4.4 AND the caching system is enabled AND UDP traffic containing cleartext sensitive data is observable on the network.

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
Upgrade available Upgrade to 10.4.4 or later
Fixed in 10.4.4
Interim mitigation

Upgrade COMOS to version V10.4.4 or later to obtain the patch; alternatively, implement network segmentation and firewall rules to restrict UDP access from untrusted networks.

Recommended fix Moderate confidence

COMOS V10.4.4

  1. 1. Identify the current COMOS version installed in your environment
  2. 2. Navigate to the Siemens Product Support website (support.industry.siemens.com) or cert-portal.siemens.com
  3. 3. Locate COMOS V10.4.4 or later from the software downloads section
  4. 4. Review the V10.4.4 release notes and upgrade documentation for your specific COMOS edition
  5. 5. Create a complete backup of your COMOS database and project files before upgrading
  6. 6. Follow the standard COMOS upgrade procedure documented in the Siemens installation guide
  7. 7. Verify the upgrade was successful by checking the COMOS version information
  8. 8. Validate that the caching system is no longer transmitting sensitive data via UDP
Caveat Review Siemens release notes for V10.4.4 for any compatibility changes or deprecations that may affect your existing projects or integrations

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

Fix this in Comos Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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