dbcve.org
Scalance W700 Series FirmwareOperating system · Siemens

CVE-2013-4652

HIGH · 10.0 CVSS v2.0 Published 2013-08-01
Fix available
A fix is available. Upgrade to after 4.4.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in the command-line management interface on Siemens Scalance W7xx devices with firmware before 4.5.4 allows remote attackers to bypass authentication and execute arbitrary code via a (1) SSH or (2) TELNET connection.

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 confidence

Unspecified authentication bypass vulnerability in the command-line management interface of Siemens Scalance W7xx wireless devices allows remote attackers to bypass authentication via SSH or TELNET connections, enabling arbitrary code execution. The vulnerability exists in firmware versions prior to 4.5.4.

MitigationUpdate Scalance W7xx firmware to version 4.5.4 or later. Additionally, restrict SSH/TELNET access to the management interface by isolating these services behind a jump host or VPN, limiting exposure to trusted management networks until the patch can be applied.

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
Scalance W700 Series FirmwareOperating system
Affected:<= 4.4.0
Scalance W744 1Hardware / appliance
Affected:all versions
Scalance W744 1proHardware / appliance
Affected:all versions
Scalance W746 1Hardware / appliance
Affected:all versions
Scalance W746 1proHardware / appliance
Affected:all versions
Scalance W747 1Hardware / appliance
Affected:all versions
Scalance W747 1rrHardware / appliance
Affected:all versions
Scalance W784 1Hardware / appliance
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Scalance W7xx model
    Check the device hardware label, web management interface device info page, or CLI output for the exact model number (W744 1, W746 1, W747 1, W784 1, etc.)
    Affected if The device is any of the listed models: W744 1, W744 1pro, W746 1, W746 1pro, W747 1, W747 1rr, W784 1, or W700 Series running firmware <= 4.4.0
  2. Check the firmware version
    Access the web management interface and navigate to the device information or firmware version page, or use the CLI command 'show version' or 'info' to retrieve the installed firmware version
    Affected if The firmware version is below 4.5.4, or for W744 1, W744 1pro, W746 1, W746 1pro, W747 1, W747 1rr, or W784 1: any version since these are listed as affected for all versions
  3. Verify if SSH management is enabled
    Check the device configuration for SSH service settings, typically found in the network services or management access section of the web interface or CLI with 'show services' or 'show ssh config'
    Affected if SSH is enabled and the service is accessible on the network
  4. Verify if TELNET management is enabled
    Check the device configuration for TELNET service settings in the network services or management access section of the web interface or CLI, or attempt to connect to port 23
    Affected if TELNET is enabled and port 23 is reachable
  5. Assess network exposure of management interfaces
    Scan network accessibility of ports 22 (SSH) and 23 (TELNET) from untrusted network segments, or review firewall rules and ACLs protecting the device management interfaces
    Affected if SSH or TELNET management ports are reachable from outside trusted management networks

The environment is affected if the device is a Siemens Scalance W7xx model running firmware prior to 4.5.4 (or any version for W744/W746/W747/W784 models) and has SSH or TELNET management interfaces enabled and accessible from the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 4.4.0
Interim mitigation

Update Scalance W7xx firmware to version 4.5.4 or later. Additionally, restrict SSH/TELNET access to the management interface by isolating these services behind a jump host or VPN, limiting exposure to trusted management networks until the patch can be applied.

Recommended fix High confidence

Firmware version 4.5.4 or later (Siemens Scalance W7xx series)

  1. 1. Identify the current firmware version of the Scalance W7xx device via the web interface or CLI
  2. 2. Download the firmware version 4.5.4 or later from the Siemens support website (www.siemens.com)
  3. 3. Access the device management interface via web browser
  4. 4. Navigate to the firmware update section (typically under 'System' > 'Firmware' or 'Maintenance' > 'Update')
  5. 5. Upload the downloaded firmware file and initiate the update
  6. 6. Wait for the update process to complete and the device to reboot
  7. 7. Verify the new firmware version is installed and the device is operational
  8. 8. After upgrade, verify that SSH and TELNET access require proper authentication
Caveat Review Siemens release notes for 4.5.4+ for any configuration or feature changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Scalance W700 Series Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,700
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,320.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-4652 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-4652 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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