CVE-2023-29130
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 CN 4100 (All versions < V2.5). Affected device consists of improper access controls in the configuration files that leads to privilege escalation. An attacker could gain admin access with this vulnerability leading to complete device control.
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 confidenceSIMATIC CN 4100 devices running versions prior to V2.5 contain improper access controls in configuration files that allow an unauthenticated attacker to escalate privileges to administrator level, achieving complete device control.
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< 2.5CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device web interface, PLC engineering software, or device management console and confirm the model is SIMATIC CN 4100Affected if The device is not a SIMATIC CN 4100 model
-
Check the installed firmware versionAccess the device web interface under System > Firmware or Use STEP 7 (TIA Portal) to read the firmware version from the device online diagnosticsAffected if The firmware version is below V2.5 (e.g., V2.4, V2.3, V2.2, etc.)
-
Verify configuration file access controlsIf you have command-line or file system access, examine the configuration files in /etc/config/ or similar paths for world-readable or group-readable permissions that should be restricted to admin onlyAffected if Configuration files are readable by unauthenticated or non-privileged users
The environment is affected if the SIMATIC CN 4100 device is running firmware version V2.5 or earlier, as the improper access controls in configuration files allow privilege escalation.
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.5
Upgrade SIMATIC CN 4100 firmware to version V2.5 or later to remediate the improper access control vulnerability in configuration files.
V2.5
- Obtain the V2.5 firmware for SIMATIC CN 4100 from the official Siemens CERT portal or support website (refer to SSA-313488 for patch details)
- Review Siemens upgrade documentation for SIMATIC CN 4100 before proceeding
- Upload and install the V2.5 firmware following the standard Siemens firmware update procedure for the device
- After completing the upgrade, verify the device is running V2.5 and that services are functioning normally
- As a security best practice after any firmware update that addresses privilege escalation, change the admin credentials to a strong, unique password
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29130 — 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-2023-29130 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