CVE-2013-4651
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 Scalance W7xx devices with firmware before 4.5.4 use the same hardcoded X.509 certificate across different customers' installations, which makes it easier for remote attackers to conduct man-in-the-middle attacks against SSL sessions by leveraging the certificate's trust relationship.
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 Scalance W7xx devices with firmware versions prior to 4.5.4 ship with an identical hardcoded X.509 certificate across all customer installations. This shared certificate allows any attacker who obtains or derives the certificate to perform man-in-the-middle attacks by impersonating the device and establishing trusted SSL/TLS sessions with legitimate clients.
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.4.0all 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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Complete
AV:N/AC:H/Au:N/C:P/I:P/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 device modelAccess the Scalance W7xx device web interface or CLI and check the device information page to confirm the exact model (W744 1, W744 1pro, W746 1, W746 1pro, W747 1, W747 1rr, or W784 1)Affected if The device model is any of W744 1, W744 1pro, W746 1, W746 1pro, W747 1, W747 1rr, or W784 1 (all versions affected)
-
Check firmware versionIn the device web interface, navigate to System > Device Information or use the CLI command 'show version' to retrieve the installed firmware versionAffected if The firmware version is 4.4.0 or lower, or if the device is any of the listed models at any firmware version (including versions below 4.5.4)
-
Verify certificate uniquenessExport or view the X.509 certificate presented by the device during SSL/TLS handshake (accessible via the web interface under Security > Certificates or via openssl s_client connection). Compare the certificate subject/serial across multiple devices if possibleAffected if The certificate serial number or subject matches what is known to be the hardcoded default certificate, indicating it has not been replaced with a unique per-installation certificate
A user is affected if their Scalance W7xx device is any of the listed models (W744 1, W744 1pro, W746 1, W746 1pro, W747 1, W747 1rr, W784 1) at any firmware version, or if the firmware is version 4.4.0 or lower for the W700 series, and the device is still using the default hardcoded certificate rather than a unique per-installation certificate.
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 dataUpdate all affected Scalance W7xx devices to firmware version 4.5.4 or later, which replaces the hardcoded certificate with unique per-installation certificates. After updating, verify that SSL/TLS connections establish successfully and that certificate validation operates correctly.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4651 — 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-4651 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