dbcve.org
Cerberus DmsApplication · Siemens

CVE-2022-33139

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Cerberus DMS (All versions), Desigo CC (All versions), Desigo CC Compact (All versions), SIMATIC WinCC OA V3.16 (All versions in default configuration), SIMATIC WinCC OA V3.17 (All versions in non-default configuration), SIMATIC WinCC OA V3.18 (All versions in non-default configuration). Affected applications use client-side only authentication, when neither server-side authentication (SSA) nor Kerberos authentication is enabled. In this configuration, attackers could impersonate other users or exploit the client-server protocol without being authenticated.

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

Affected applications (Cerberus DMS, Desigo CC, SIMATIC WinCC OA) rely solely on client-side authentication validation. When neither Server-Side Authentication (SSA) nor Kerberos authentication is enabled, the server blindly trusts authentication tokens presented by the client, allowing attackers to impersonate users or interact with the client-server protocol without valid credentials.

MitigationEnable Server-Side Authentication (SSA) or Kerberos authentication on affected applications to enforce server-side credential validation.

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
Cerberus DmsApplication
Affected:all versions
Desigo CcApplication
Affected:all versions
Desigo Cc CompactApplication
Affected:all versions
Wincc Open ArchitectureApplication
Affected:= 3.16= 3.17= 3.18

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. Identify installed affected product
    Determine which of the following products is installed: Cerberus DMS, Desigo CC, Desigo CC Compact, or SIMATIC WinCC Open Architecture (versions 3.16, 3.17, or 3.18)
    Affected if Any of these products are present in the environment
  2. Locate authentication configuration
    Access the security or authentication settings panel within the installed product (typically found in the system administration or configuration management section)
    Affected if Access to authentication settings is possible and SSA or Kerberos options are available
  3. Check Server-Side Authentication (SSA) status
    Inspect the authentication configuration to determine whether Server-Side Authentication is enabled or disabled
    Affected if SSA is explicitly disabled or set to a mode that relies solely on client-side validation
  4. Check Kerberos authentication status
    Inspect the authentication configuration to determine whether Kerberos authentication is enabled or disabled
    Affected if Kerberos authentication is disabled or not configured
  5. Determine vulnerability status
    Review both SSA and Kerberos settings: if SSA is disabled AND Kerberos is not enabled, the server trusts client-provided authentication tokens
    Affected if Both Server-Side Authentication is disabled AND Kerberos authentication is not enabled

If neither Server-Side Authentication (SSA) nor Kerberos authentication is enabled in Cerberus DMS, Desigo CC, or WinCC Open Architecture, the environment is affected by this vulnerability.

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

Enable Server-Side Authentication (SSA) or Kerberos authentication on affected applications to enforce server-side credential validation.

Recommended fix Moderate confidence
  1. 1. Identify all affected Siemens applications (Cerberus DMS, Desigo CC, Desigo CC Compact, WinCC OA versions 3.16-3.18) in the environment
  2. 2. Review current authentication configuration for each affected application
  3. 3. Enable Server-Side Authentication (SSA) as the primary mitigation, or alternatively enable Kerberos authentication
  4. 4. After enabling SSA or Kerberos authentication, verify that client-side only authentication is disabled
  5. 5. Test authentication flows to confirm the configuration change is effective
  6. 6. Document the configuration change for compliance and audit purposes
Caveat Enabling SSA or Kerberos authentication may require coordination with downstream systems and clients; test thoroughly in staging before production deployment

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

Fix this in Cerberus Dms Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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