CVE-2020-7589
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). The vulnerability could lead to an attacker reading and modifying the device configuration and obtain project files from affected devices. The security vulnerability could be exploited by an unauthenticated attacker with network access to port 135/tcp. No user interaction is required to exploit this security vulnerability. The vulnerability impacts confidentiality, integrity, and availability of the device. At the time of advisory publication no public exploitation of this security vulnerability was known.
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 unauthenticated remote code execution or configuration manipulation vulnerability in Siemens LOGO! 8 PLCs. An attacker with network access to port 135/tcp (DCOM) can read and modify device configuration and extract project files without any credentials, impacting confidentiality, integrity, and availability of the industrial device.
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 dataall versionsCVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 Siemens LOGO! 8 device on the networkUse network scanning tools (such as Nmap) or check DHCP/asset inventories for devices advertising the LOGO! 8 web server on port 80/8080, or look for Siemens LOGO! device fingerprints in network traffic.Affected if A Siemens LOGO! 8 PLC is present on the network.
-
Verify port 135/tcp is exposedPerform a port scan targeting the LOGO! 8 device IP address on port 135/tcp (for example: nmap -p 135 <target_ip>). Alternatively, review firewall rules and network boundary devices to determine if port 135/tcp is accessible from untrusted networks.Affected if Port 135/tcp returns as open or is permitted through perimeter firewalls.
-
Check the device firmware versionAccess the LOGO! 8 web interface (if enabled) or use Siemens LOGO! Soft Comfort software to connect to the device and retrieve the firmware version from the device properties or system information.Affected if The device firmware version is any version of Siemens LOGO! 8 (all versions are affected per the CVE).
-
Confirm DCOM remote configuration is enabledWithin the LOGO! 8 web interface or LOGO! Soft Comfort, check the device settings for remote access or DCOM configuration options. If the device allows remote configuration via DCOM without authentication, the vulnerability is exploitable.Affected if Remote configuration or DCOM access is enabled on the device.
A user is affected if a Siemens LOGO! 8 PLC with any firmware version has port 135/tcp exposed and DCOM remote configuration is enabled.
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.
From vendor dataRestrict network access to port 135/tcp using firewalls or network segmentation, apply Siemens firmware updates when available, and monitor for unauthorized access attempts on affected devices.
- Consultation12.0 h
- Implementation16.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 $13,056.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7589 — 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-7589 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