dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2024-33698

CRITICAL · 9.8 CVSS v3.1 Published 2024-09-10
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 Opcenter Quality (All versions < V2406), Opcenter RDnL (All versions < V2410), SIMATIC PCS neo V4.0 (All versions), SIMATIC PCS neo V4.1 (All versions < V4.1 Update 2), SIMATIC PCS neo V5.0 (All versions < V5.0 Update 1), SINEC NMS (All versions), SINEMA Remote Connect Client (All versions < V3.2 SP3), Totally Integrated Automation Portal (TIA Portal) V16 (All versions), Totally Integrated Automation Portal (TIA Portal) V17 (All versions < V17 Update 8), Totally Integrated Automation Portal (TIA Portal) V18 (All versions < V18 Update 5), Totally Integrated Automation Portal (TIA Portal) V19 (All versions < V19 Update 3). Affected products contain a heap-based buffer overflow vulnerability in the integrated UMC component. This could allow an unauthenticated remote attacker to execute arbitrary code.

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

Heap-based buffer overflow vulnerability in the integrated UMC (User Management Component) across multiple Siemens industrial automation software products. This memory corruption flaw allows unauthenticated remote attackers to execute arbitrary code by overflowing heap-allocated buffers through specially crafted input to the UMC service.

MitigationApply vendor-supplied patches: Opcenter Quality V2406+, Opcenter RDnL V2410+, SIMATIC PCS neo V4.1 Update 2+, V5.0 Update 1+, TIA Portal V17 Update 8+, V18 Update 5+, V19 Update 3+, SINEMA Remote Connect Client V3.2 SP3+. For products with no fixed version (PCS neo V4.0, SINEC NMS), contact Siemens for alternative mitigations.

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
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 Siemens industrial software product
    Open Windows Programs and Features (appwiz.cpl) or check installation directories for Siemens software such as Opcenter Quality, Opcenter RDnL, SIMATIC PCS neo, TIA Portal, SINEMA Remote Connect Client, or SINEC NMS. Note the exact product name and version.
    Affected if Any of these Siemens products with UMC (User Management Component) are installed and the version falls within or before the fixed versions (Opcenter Quality <V2406, Opcenter RDnL <V2410, SIMATIC PCS neo <V4.1 U2 or <V5.0 U1, TIA Portal <V17 U8, <V18 U5, or <V19 U3, SINEMA Remote Connect Client <V3.2
  2. Locate and verify UMC service status
    Open Windows Services (services.msc) and look for services containing 'User Management', 'UMC', or 'Siemens' in the name. Check if the service is running or set to start automatically.
    Affected if The UMC service is installed and running (the vulnerability is in the UMC component itself)
  3. Check product version against vulnerable ranges
    Use the product's About dialog, check installation logs, or query the installed version via registry under HKLM\SOFTWARE\Siemens\ProductName\Version (path varies by product). Compare against known vulnerable version ranges.
    Affected if Installed version is before the fixed versions listed in the vendor advisory (see step 1 for specific thresholds)
  4. Verify UMC network exposure
    Check Windows Firewall rules or product configuration for ports or services exposing UMC. Review product documentation or configuration files for UMC server settings, typically found in installation directories under config or settings folders.
    Affected if UMC service is accessible over the network (the vulnerability allows remote unauthenticated exploitation)

You are affected if any of these Siemens products (Opcenter Quality, Opcenter RDnL, SIMATIC PCS neo, TIA Portal, SINEMA Remote Connect Client, SINEC NMS) are installed with UMC enabled, and the installed version is before the patched versions OR has no available patch.

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

Apply vendor-supplied patches: Opcenter Quality V2406+, Opcenter RDnL V2410+, SIMATIC PCS neo V4.1 Update 2+, V5.0 Update 1+, TIA Portal V17 Update 8+, V18 Update 5+, V19 Update 3+, SINEMA Remote Connect Client V3.2 SP3+. For products with no fixed version (PCS neo V4.0, SINEC NMS), contact Siemens for alternative mitigations.

Recommended fix High confidence

Upgrade to the minimum fixed version specified for each product (V2406 for Opcenter Quality, V2410 for Opcenter RDnL, V4.1 Update 2 for PCS neo V4.1, V5.0 Update 1 for PCS neo V5.0, V3.2 SP3 for SINEMA Remote Connect, V17 Update 8/V18 Update 5/V19 Update 3 for TIA Portal)

  1. 1. Identify the specific Siemens product and version currently installed from the list: Opcenter Quality, Opcenter RDnL, SIMATIC PCS neo, SINEC NMS, SINEMA Remote Connect Client, or TIA Portal (V16-V19)
  2. 2. For Opcenter Quality: Upgrade to version V2406 or later
  3. 3. For Opcenter RDnL: Upgrade to version V2410 or later
  4. 4. For SIMATIC PCS neo V4.0: No fixed version available; contact Siemens for guidance or consider upgrading to a supported release
  5. 5. For SIMATIC PCS neo V4.1: Upgrade to V4.1 Update 2 or later
  6. 6. For SIMATIC PCS neo V5.0: Upgrade to V5.0 Update 1 or later
  7. 7. For SINEC NMS: No fixed version available in the advisory; contact Siemens for remediation guidance
  8. 8. For SINEMA Remote Connect Client: Upgrade to V3.2 SP3 or later
Caveat Older product versions (e.g., TIA Portal V16, SIMATIC PCS neo V4.0, SINEC NMS) have no fix available and may require migration to newer major versions; review Siemens product lifecycle documentation for compatibility and migration requirements

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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