Sm 2556 FirmwareOperating system · Siemens

CVE-2017-12737

MEDIUM · 5.3 CVSS v3.0 Published 2017-11-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
An issue was discovered on Siemens SICAM RTUs SM-2556 COM Modules with the firmware variants ENOS00, ERAC00, ETA2, ETLS00, MODi00, and DNPi00. The integrated web server (port 80/tcp) of the affected devices could allow unauthenticated remote attackers to obtain sensitive device information over the network.

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

The Siemens SICAM RTUs SM-2556 COM Modules with multiple firmware variants contain an unauthenticated information disclosure vulnerability in their integrated web server on port 80/tcp. Remote attackers can obtain sensitive device information without any authentication credentials.

MitigationRestrict network access to port 80/tcp through firewall rules or network segmentation to prevent untrusted external access. If authentication can be enabled on the web server, implement it immediately.

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
Sm 2556 FirmwareOperating system
Affected:= dnpi00= enos00= erac00= eta2= etls00= modi00

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

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

  1. Identify Siemens SM-2556 COM Module on the network
    Scan the network for devices responding on port 80/tcp and check the HTTP server banner or device web page for identifiers matching the SM-2556 COM module product name. Alternatively, review network documentation or asset inventories for Siemens SICAM RTU devices.
    Affected if The device is a Siemens SICAM RTU SM-2556 COM Module.
  2. Determine the firmware version
    Access the device web interface (port 80/tcp) and navigate to the system information or firmware version page. If the page is accessible without authentication, the firmware variant name (such as dnpi00, enos00, erac00, eta2, etls00, or modi00) will be displayed.
    Affected if The displayed firmware variant is one of: dnpi00, enos00, erac00, eta2, etls00, or modi00.
  3. Confirm the web server is accessible on port 80/tcp
    Use a port scanner or netcat to verify that port 80/tcp is open and accepting connections on the target device: nc -zv <target_ip> 80 or nmap -p 80 <target_ip>
    Affected if Port 80/tcp is open and responds to HTTP requests.
  4. Verify unauthenticated access to sensitive information
    Send an HTTP GET request to the device without providing any authentication credentials (for example: curl http://<target_ip>/ or curl http://<target_ip>/device_info). Check if the response contains sensitive device information such as configuration details, network settings, or system data without requiring a login.
    Affected if Sensitive device information is returned without any authentication required.

You are affected if the target is a Siemens SM-2556 COM Module running one of the affected firmware variants (dnpi00, enos00, erac00, eta2, etls00, or modi00) and its web server on port 80/tcp returns sensitive information without authentication.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to port 80/tcp through firewall rules or network segmentation to prevent untrusted external access. If authentication can be enabled on the web server, implement it immediately.

Fix this in Sm 2556 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12737 — 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-2017-12737 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