CVE-2025-30175
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 · uneditedA vulnerability has been identified in SIMATIC PCS neo V4.1 (All versions), SIMATIC PCS neo V5.0 (All versions), SINEC NMS (All versions < V4.0), SINEMA Remote Connect (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), Totally Integrated Automation Portal (TIA Portal) V20 (All versions), User Management Component (UMC) (All versions < V2.15.1.1). Affected products contain a out of bound write buffer overflow vulnerability in the integrated UMC component. This could allow an unauthenticated remote attacker to cause a denial of service condition.
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 confidenceA buffer overflow vulnerability exists in the User Management Component (UMC) integrated into multiple Siemens industrial software products. The out-of-bounds write condition can be triggered by an unauthenticated remote attacker, leading to denial of service.
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= 4.1= 5.0< 4.0all versions= 17= 18= 19= 20< 2.15.1.1CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Siemens industrial software productReview installed programs or running services to determine which Siemens product is present: Simatic PCS neo, SINEC NMS, SINEMA Remote Connect, TIA Portal, or standalone UMCAffected if Any of the following products are installed: Simatic PCS neo versions 4.1 or 5.0, SINEC NMS versions below 4.0, SINEMA Remote Connect any version, TIA Portal versions 17-20, or UMC versions below 2.15.1.1
-
Check Simatic PCS neo versionLocate the installation directory or check Add/Remove Programs for the version number of Simatic PCS neoAffected if Installed version equals 4.1 or equals 5.0
-
Check SINEC NMS versionLocate the installation directory or check Add/Remove Programs for the version number of SINEC NMSAffected if Installed version is less than 4.0
-
Check SINEMA Remote Connect versionLocate the installation directory or check Add/Remove Programs for the version number of SINEMA Remote ConnectAffected if Any version of SINEMA Remote Connect is installed (all versions are affected)
-
Check TIA Portal versionLocate the installation directory or check Add/Remove Programs for the version number of Totally Integrated Automation PortalAffected if Installed version equals 17, 18, 19, or 20
-
Check UMC component versionIf using standalone UMC or if UMC component is accessible within the product, check the User Management Component version in its about or version information panelAffected if UMC version is below 2.15.1.1
Your environment is affected if any of these conditions are true: Simatic PCS neo version 4.1 or 5.0 is installed, SINEC NMS version is below 4.0, any version of SINEMA Remote Connect is installed, TIA Portal version 17-20 is installed, or UMC version is below 2.15.1.1.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.15.1.14.0
Upgrade UMC to version V2.15.1.1 or later, and apply corresponding product-specific updates from Siemens for TIA Portal, SIMATIC PCS neo, SINEC NMS, and SINEMA Remote Connect.
UMC: 2.15.1.1; SINEC NMS: V4.0
- Upgrade User Management Component (UMC) to version 2.15.1.1 or later
- For SINEC NMS, upgrade to version 4.0 or later
- For SIMATIC PCS neo, monitor Siemens security advisories for updated versions addressing this vulnerability
- For TIA Portal V17-V20 and Sinema Remote Connect, apply vendor patches when released or contact Siemens support for mitigation guidance
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30175 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-30175 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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