dbcve.org
Opcenter QualityApplication · Siemens

CVE-2021-27389

CRITICAL · 9.8 CVSS v3.1 Published 2021-04-22
Fix available
A fix is available. Upgrade to 12.2 / 12.30 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Opcenter Quality (All versions < V12.2), QMS Automotive (All versions < V12.30). A private sign key is shipped with the product without adequate protection.

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

A private signing key is bundled with Opcenter Quality and QMS Automotive installations without adequate protection. This allows attackers with access to the key to sign malicious updates, code, or communications as legitimate, effectively bypassing code-signing verification and authentication mechanisms.

MitigationUpdate Opcenter Quality to version V12.2 or later, and QMS Automotive to version V12.30 or later, as these versions remove the exposed private key from the product distribution.

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
Opcenter QualityApplication
Affected:< 12.2
Qms AutomotiveApplication
Affected:< 12.30

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
High
Availability
High

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

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. Check Opcenter Quality version
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Opcenter*Quality*'} | Select-Object Name, Version
    Affected if Version is below 12.2 (e.g., 12.0, 12.1)
  2. Check QMS Automotive version
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*QMS*Automotive*'} | Select-Object Name, Version
    Affected if Version is below V12.30 (e.g., V12.0, V12.1, V12.2)
  3. Locate Opcenter Quality installation directory
    Check default installation paths such as C:\Program Files\Siemens\Opcenter\Quality or C:\Siemens\Opcenter\Quality, or use PowerShell: Get-ChildItem -Path 'C:\Program Files\Siemens' -Recurse -Directory -ErrorAction SilentlyContinue | Where-Object {$_.Name -eq 'Quality'}
    Affected if Installation directory exists and contains a private key file (typically .pfx, .p12, .key, .pem, or .pvk extensions)
  4. Locate QMS Automotive installation directory
    Check default installation paths such as C:\Program Files\Siemens\QMS\Automotive or search using PowerShell: Get-ChildItem -Path 'C:\Program Files\Siemens' -Recurse -Directory -ErrorAction SilentlyContinue | Where-Object {$_.Name -match 'QMS|Automotive'
    Affected if Installation directory exists and contains a private key file (typically .pfx, .p12, .key, .pem, or .pvk extensions)
  5. Search for certificate or key files in installation folders
    Within the product installation directories, search for files with extensions .pfx, .p12, .key, .pem, .pvk, .cer, or .p7b using PowerShell: Get-ChildItem -Path 'C:\Program Files\Siemens\Opcenter' -Recurse -Include *.pfx,*.p12,*.key,*.pem,*.pvk -ErrorAction SilentlyContinue
    Affected if Any private key or certificate bundle files are found in the product installation folder

You are affected if Opcenter Quality is below V12.2 or QMS Automotive is below V12.30, OR if a private signing key file exists in either product's installation directory.

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.2 / 12.30 or later
Fixed in 12.212.30
Interim mitigation

Update Opcenter Quality to version V12.2 or later, and QMS Automotive to version V12.30 or later, as these versions remove the exposed private key from the product distribution.

Recommended fix High confidence

Opcenter Quality: V12.2 or later; QMS Automotive: V12.30 or later

  1. Identify whether the deployed product is Opcenter Quality or QMS Automotive
  2. For Opcenter Quality: upgrade to version 12.2 or later
  3. For QMS Automotive: upgrade to version 12.30 or later
  4. After upgrading, verify that the private sign key is no longer shipped with the product or is adequately protected
  5. Consult Siemens release notes for any additional post-upgrade configuration requirements

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

Fix this in Opcenter Quality Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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