Scalance X414 3e FirmwareApplication · Siemens

CVE-2012-1802

HIGH · 7.8 CVSS v2.0 Published 2012-04-18
Fix available
A fix is available. Upgrade to after 3.7.0 or later.
See remediation →
87/100
Remediation priority · High
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
Buffer overflow in the embedded web server on the Siemens Scalance X Industrial Ethernet switch X414-3E before 3.7.1, X308-2M before 3.7.2, X-300EEC before 3.7.2, XR-300 before 3.7.2, and X-300 before 3.7.2 allows remote attackers to cause a denial of service (device reboot) or possibly execute arbitrary code via a malformed URL.

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

Buffer overflow vulnerability in the embedded web server component of Siemens Scalance X-300 series industrial Ethernet switches allows remote attackers to cause denial of service via device reboot or potentially execute arbitrary code by sending malformed URL requests.

MitigationApply Siemens firmware updates (3.7.1 for X414-3E or 3.7.2 for X308-2M, X-300EEC, XR-300, X-300 models) to patch the vulnerability; if patching is not immediately feasible, restrict network access to the web server management interface.

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 X414 3e FirmwareApplication
Affected:<= 3.7.0= 1.2.2= 2.1.1= 2.2.0= 2.3.2= 2.3.3= 3.0.0= 3.0.2= 3.3.0= 3.4.0
Scalance X414 3eHardware / appliance
Affected:all versions
Scalance X308 2m FirmwareApplication
Affected:<= 3.7.0= 3.1.1= 3.5.0= 3.5.2
Scalance X308 2mHardware / appliance
Affected:all versions
Scalance X 300eec FirmwareApplication
Affected:<= 3.7.0= 3.5.0
Scalance X 300eecHardware / appliance
Affected:all versions
Scalance Xr 300 FirmwareApplication
Affected:<= 3.7.0= 3.1.1= 3.5.0
Scalance Xr 300Hardware / 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
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/C:N/I:N/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 device model
    Access the device console or web interface and retrieve the hardware model name. Check if the device is one of: Scalance X414 3e, Scalance X308 2m, Scalance X 300eec, or Scalance Xr 300.
    Affected if Device is NOT one of these four models - the vulnerability does not apply.
  2. Check firmware version
    Access the device web interface (typically via https) and navigate to System > Firmware or Info > Version to view the installed firmware version. Alternatively, use the device console and run 'show firmware' or similar command.
    Affected if Firmware version is <= 3.7.0 OR equals 1.2.2, 2.1.1, 2.2.0, 2.3.2, 2.3.3, 3.0.0, 3.0.2, 3.1.1, 3.3.0, 3.4.0, 3.5.0, or 3.5.2 - the device is running a vulnerable firmware version.
  3. Confirm web server is enabled
    In the device web interface, navigate to HTTP/HTTPS settings or Web-Based Management settings. Verify that the embedded web server (HTTP or HTTPS) is enabled.
    Affected if Web server is disabled - the attack surface is not present, though the vulnerable code may still exist in firmware.
  4. Verify web management accessibility
    Attempt to access the device web interface from a network location using a browser. Check if TCP ports 80 (HTTP) or 443 (HTTPS) are listening on the device and reachable from your network segment.
    Affected if The web interface is exposed to untrusted networks - remote exploitation is possible.

Device is affected if it is a Scalance X414 3e, X308 2m, X 300eec, or Xr 300 with vulnerable firmware (<=3.7.0 or specific listed versions) AND the embedded web server is enabled and network-accessible.

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.

From vendor data
Upgrade available Upgrade to a release after 3.7.0
Interim mitigation

Apply Siemens firmware updates (3.7.1 for X414-3E or 3.7.2 for X308-2M, X-300EEC, XR-300, X-300 models) to patch the vulnerability; if patching is not immediately feasible, restrict network access to the web server management interface.

Fix this in Scalance X414 3e Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-1802 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-1802 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