CVE-2013-6920
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 · uneditedSiemens SINAMICS S/G controllers with firmware before 4.6.11 do not require authentication for FTP and TELNET sessions, which allows remote attackers to bypass intended access restrictions via TCP traffic to port (1) 21 or (2) 23.
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 confidenceSiemens SINAMICS S/G controller firmware before version 4.6.11 ships with FTP (port 21) and TELNET (port 23) services that do not require authentication, allowing unauthenticated remote attackers to gain full access to these industrial control devices by connecting directly to these services.
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.6all versionsall versionsall versionsall versionsall versionsall versionsall 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 your Sinamics device modelLocate the device nameplate or check your asset inventory for the exact Sinamics model (e.g., G120, G130, S/G series)Affected if The device is any of: Sinamics G110, G110d, G120, G120c, G120d, G120p, G130, or S/G family
-
Determine the installed firmware versionAccess the device control unit or use the Sinamics engineering tool (e.g., STARTER or Startdrive) to read the firmware version from the device propertiesAffected if Firmware version is 4.6 or lower for S/G family, or any version for G110/G130 series models
-
Verify if FTP service is exposedAttempt a TCP connection to port 21 on the device IP address, or check network firewall rules allowing inbound traffic to port 21Affected if Port 21 is open and accepts FTP connections without prompting for credentials
-
Verify if TELNET service is exposedAttempt a TCP connection to port 23 on the device IP address, or check network firewall rules allowing inbound traffic to port 23Affected if Port 23 is open and provides shell access without prompting for authentication
You are affected if your Sinamics device is any G110/G130 series (all versions) or S/G family with firmware <=4.6, AND either FTP (port 21) or TELNET (port 23) is accessible on the network without authentication.
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 · scopedUpdate SINAMICS S/G firmware to version 4.6.11 or later to enable authentication, or disable FTP and TELNET services entirely if not required and use alternative secure protocols.
SINAMICS S/G firmware 4.6.11 or later (contact Siemens for patched firmware for G-series devices)
- 1. Identify the specific Sinamics device model and its current firmware version by accessing the device or its management interface
- 2. For SINAMICS S/G controllers: Determine if the current firmware version is before 4.6.11 (vulnerable)
- 3. For SINAMICS G110, G110d, G120, G120c, G120d, G120p, G130: Note that all versions are affected; check Siemens for any available firmware updates
- 4. Download the patched firmware from Siemens support portal (cert-portal.siemens.com or siemens.com) - ensure the version is 4.6.11 or later for S/G
- 5. Follow Siemens' official firmware update procedure for your specific device model
- 6. After updating, verify the firmware version is 4.6.11 or higher
- 7. As a configuration mitigation: If FTP/TELNET are not required for operations, disable these services on the device
- 8. If these services are required, implement network segmentation to restrict access to trusted networks only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6920 — 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-2013-6920 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