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

CVE-2024-49775

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-16
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 Execution Foundation (All versions < V2501.0001), Opcenter Intelligence (All versions < V2501.0001), Opcenter Quality (All versions < V2512), Opcenter RDnL (All versions < V2410), SIMATIC PCS neo V4.0 (All versions), SIMATIC PCS neo V4.1 (All versions < V4.1 Update 3), SIMATIC PCS neo V5.0 (All versions < V5.0 Update 1), SINEC NMS (All versions if operated in conjunction with UMC < V2.15), Totally Integrated Automation Portal (TIA Portal) V16 (All versions), Totally Integrated Automation Portal (TIA Portal) V17 (All versions), Totally Integrated Automation Portal (TIA Portal) V18 (All versions), Totally Integrated Automation Portal (TIA Portal) V19 (All versions). 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 in the integrated UMC (User Management Component) allows unauthenticated remote attackers to execute arbitrary code on affected Siemens industrial software products including Opcenter, SIMATIC PCS neo, SINEC NMS, and TIA Portal.

MitigationApply vendor-supplied patches to reach version thresholds (V2501.0001 or higher for Opcenter products, V4.1 Update 3 or V5.0 Update 1 for SIMATIC PCS neo, V2.15 for SINEC NMS, V19 for TIA Portal); isolate affected systems from untrusted networks as interim control.

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
    Check your system for installed Opcenter, SIMATIC PCS neo, SINEC NMS, or TIA Portal products using system inventory tools or Add/Remove Programs
    Affected if Any of these four products are installed on the system
  2. Determine installed product version
    Locate the product version through the software's About dialog, installation directory version file, or Windows Programs and Features entry
    Affected if The installed version falls below V2501.0001 for Opcenter, below V4.1 Update 3 or V5.0 Update 1 for SIMATIC PCS neo, below V2.15 for SINEC NMS, or below V19 for TIA Portal
  3. Verify UMC component is present
    Check if the User Management Component (UMC) service or module is running on the system, typically found in the software's installation directory or as a Windows service
    Affected if UMC is installed and running as part of the Siemens software installation
  4. Assess network exposure of UMC service
    Review firewall rules and network configuration to determine if the UMC service ports are accessible from untrusted networks or the internet
    Affected if UMC ports are exposed to untrusted or external networks without proper network segmentation

You are affected if you have any of the four listed Siemens products installed with a version below the thresholds AND the UMC component is active and network-accessible from untrusted sources.

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 to reach version thresholds (V2501.0001 or higher for Opcenter products, V4.1 Update 3 or V5.0 Update 1 for SIMATIC PCS neo, V2.15 for SINEC NMS, V19 for TIA Portal); isolate affected systems from untrusted networks as interim control.

Recommended fix High confidence

V2501.0001 (Opcenter Execution Foundation/Intelligence), V2512 (Opcenter Quality), V2410 (Opcenter RDnL), V4.1 Update 3 or V5.0 Update 1 (SIMATIC PCS neo), V2.15 (UMC for SINEC NMS), V19 (TIA Portal)

  1. 1. Identify the specific Siemens product in use from the affected product list (Opcenter Execution Foundation, Opcenter Intelligence, Opcenter Quality, Opcenter RDnL, SIMATIC PCS neo, SINEC NMS, or TIA Portal)
  2. 2. For Opcenter Execution Foundation: Upgrade to version V2501.0001 or later
  3. 3. For Opcenter Intelligence: Upgrade to version V2501.0001 or later
  4. 4. For Opcenter Quality: Upgrade to version V2512 or later
  5. 5. For Opcenter RDnL: Upgrade to version V2410 or later
  6. 6. For SIMATIC PCS neo V4.0: Upgrade to V4.1 Update 3 or later, or migrate to a supported version
  7. 7. For SIMATIC PCS neo V4.1: Upgrade to V4.1 Update 3 or later
  8. 8. For SIMATIC PCS neo V5.0: Upgrade to V5.0 Update 1 or later
Caveat Upgrading TIA Portal major versions may require project migration and compatibility testing; Opcenter upgrades may require system downtime and database migration steps

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

Have this fixed Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
60.0 hours of engineering $10,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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