CVE-2020-25228
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 LOGO! 8 BM (incl. SIPLUS variants) (All versions < V8.3). A service available on port 10005/tcp of the affected devices could allow complete access to all services without authorization. An attacker could gain full control over an affected device, if he has access to this service. The system manual recommends to protect access to this port.
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 confidenceThis is an authentication bypass vulnerability in Siemens LOGO! 8 BM PLC devices. A service listening on port 10005/tcp allows complete, unauthorized access to all device services, enabling an attacker to gain full control of the affected PLC. All versions prior to V8.3 are vulnerable.
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< 8.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the PLC web interface or use SNMP to query the device and confirm it is a Siemens LOGO! 8 BM series programmable logic controllerAffected if The device is a Siemens LOGO! 8 BM
-
Check the firmware versionLog into the LOGO! web server or use the LOGO! Comfort software to read the firmware version from the device properties or status pageAffected if The firmware version is earlier than V8.3 (for example, V8.2, V8.1, V8.0, or earlier)
-
Verify port 10005/tcp is exposedUse a network scanner (such as nmap) to test if port 10005/tcp is open and accepting connections on the device IP address: nmap -p 10005 <device_ip>Affected if Port 10005/tcp is open and accessible from the network
The device is affected if it is a Siemens LOGO! 8 BM with firmware version prior to V8.3 AND port 10005/tcp is open and reachable on the network.
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 · scoped8.3
Upgrade LOGO! 8 BM devices to firmware version V8.3 or later. Additionally, implement network segmentation and firewall controls to restrict access to port 10005/tcp, as recommended in the system manual.
LOGO! 8 BM firmware V8.3 or later
- Identify all affected LOGO! 8 BM devices in the environment running firmware versions prior to V8.3
- Obtain the LOGO! 8 BM firmware V8.3 or later from Siemens (via cert-portal.siemens.com or official Siemens channels)
- Review the Siemens firmware upgrade documentation for LOGO! 8 BM devices
- Schedule a maintenance window for each affected device
- Backup the current device configuration if supported
- Upload and install the firmware V8.3 or later onto each affected device following Siemens' upgrade procedure
- Verify the firmware version has been successfully updated
- Confirm the port 10005/tcp service now requires proper authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25228 — 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-2020-25228 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