dbcve.org
Qms AutomotiveApplication · Siemens

CVE-2023-40729

HIGH · 7.4 CVSS v3.1 Published 2023-09-12
Fix available
A fix is available. Upgrade to 12.39 or later.
See remediation →
83/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 QMS Automotive (All versions < V12.39). The affected application lacks security control to prevent unencrypted communication without HTTPS. An attacker who managed to gain machine-in-the-middle position could manipulate, or steal confidential information.

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

QMS Automotive versions prior to V12.39 lack security controls to enforce HTTPS encryption, allowing unencrypted HTTP communications. An attacker with man-in-the-middle position could intercept, manipulate, or steal confidential data transmitted between clients and the application server.

MitigationUpgrade QMS Automotive to version V12.39 or later and ensure proper HTTPS/TLS configuration is enforced for all communications.

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
Qms AutomotiveApplication
Affected:< 12.39

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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. Identify installed QMS Automotive version
    Access the QMS Automotive application or system information panel, typically found in the application's About section, Help menu, or system registry under the Siemens installation directory. Run 'msiexec /x {product-code}' or check the Windows Programs and Features list for the installed version.
    Affected if The displayed version is below V12.39 (e.g., V12.38, V12.0, V11.x, etc.)
  2. Verify HTTPS enforcement in server configuration
    Locate the QMS Automotive server configuration file (commonly named server.config, web.config, or similar in the installation directory under Config or Settings folder). Inspect the binding, protocol, or security settings to determine if HTTPS is explicitly required.
    Affected if The configuration shows HTTP is enabled without requiring SSL/TLS, or the security setting is set to allow unencrypted connections
  3. Check SSL/TLS certificate binding
    Run 'netsh http show sslcert' or check IIS/Apache/Nginx bindings if QMS Automotive runs under a web server. Verify that port 443 (HTTPS) is bound to a valid certificate and enabled.
    Affected if Port 443 has no SSL certificate binding, or the binding exists but is not linked to the QMS Automotive application
  4. Inspect client connection settings
    Review client-side configuration files or registry settings on machines running QMS Automotive client. Look for connection strings or URL entries in config files under the client installation directory.
    Affected if Client configuration contains HTTP URLs (http://) rather than HTTPS URLs (https://), or allows fallback to unencrypted connections
  5. Test network communication for encryption
    Use a network capture tool (Wireshark, tcpdump) or browser developer tools to observe the actual traffic when the QMS Automotive client connects to the server. Attempt to access the application and inspect the initial connection protocol.
    Affected if The traffic capture shows cleartext HTTP traffic on port 80, or the server responds with HTTP 301/302 redirects to HTTP instead of enforcing HTTPS

You are affected if your QMS Automotive version is below V12.39 AND HTTP (unencrypted) connections are permitted or not explicitly blocked in your configuration.

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 12.39 or later
Fixed in 12.39
Interim mitigation

Upgrade QMS Automotive to version V12.39 or later and ensure proper HTTPS/TLS configuration is enforced for all communications.

Recommended fix Moderate confidence

V12.39 or later

  1. Upgrade QMS Automotive to version 12.39 or later to obtain the fix for the cleartext transmission vulnerability
  2. After upgrading, verify that HTTPS is enforced for all communications within the application
  3. Review application settings to confirm encryption controls are properly enabled
  4. Test the implementation to ensure all communication channels now use TLS/HTTPS

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

Fix this in Qms Automotive Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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