dbcve.org
Simatic Cp 343 1 FirmwareOperating system · Siemens

CVE-2016-8672

MEDIUM · 5.3 CVSS v3.0 Published 2016-11-23
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
A vulnerability has been identified in SIMATIC CP 343-1 Advanced (incl. SIPLUS NET variant) (All versions < V3.0.53), SIMATIC CP 443-1 Advanced (incl. SIPLUS NET variant) (All versions < V3.2.17), SIMATIC S7-300 PN/DP CPU family (incl. SIPLUS variants) (All versions), SIMATIC S7-400 PN/DP CPU family (incl. SIPLUS variants) (All versions). The integrated web server delivers cookies without the "secure" flag. Modern browsers interpreting the flag would mitigate potential data leakage in case of clear text transmission.

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 integrated web servers in SIMATIC CP 343-1 Advanced, CP 443-1 Advanced, S7-300 PN/DP, and S7-400 PN/DP devices transmit cookies without the 'secure' flag. This allows cookies to be sent over unencrypted HTTP connections, enabling potential session hijacking or data leakage through man-in-the-middle attacks on cleartext transmissions.

MitigationUpdate affected devices to the specified minimum versions (CP 343-1 Advanced: V3.0.53, CP 443-1 Advanced: V3.2.17, S7-300/400: consult Siemens for available patches). Alternatively, ensure all web server access occurs exclusively over HTTPS to mitigate cleartext cookie exposure.

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
Simatic Cp 343 1 FirmwareOperating system
Affected:all versions
Simatic S7 300 Cpu FirmwareOperating system
Affected:all versions
Simatic S7 400 Cpu FirmwareOperating system
Affected:all versions
Simatic Cp 443 1 FirmwareOperating system
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
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 the device model
    Locate the Siemens SIMATIC device model number (CP 343-1 Advanced, CP 443-1 Advanced, S7-300, or S7-400) on the physical hardware labeling or in the device's hardware configuration in TIA Portal or Step 7. Confirm it matches one of the affected product lines.
    Affected if The device is a CP 343-1 Advanced, CP 443-1 Advanced, S7-300 PN/DP, or S7-400 PN/DP.
  2. Verify the integrated web server is enabled
    In the device's web server settings (accessible via the device's IP address in a browser), navigate to the web server configuration section. Check if the 'Enable web server' or similar option is checked/active.
    Affected if The integrated web server is enabled on the device.
  3. Confirm HTTP access is allowed
    Attempt to access the device's web interface using http://[device-ip] (port 80). If the connection succeeds or redirects to HTTP, HTTP access is enabled. Also check the web server configuration for any HTTP/HTTPS port settings.
    Affected if HTTP (port 80) access to the web server is permitted or not blocked.
  4. Inspect cookie attributes via traffic capture
    Using a network capture tool (such as Wireshark) or a browser's developer tools, capture network traffic while authenticating to the device's web interface over HTTP. Examine the Set-Cookie headers in the HTTP responses to determine if the 'Secure' attribute is present on session cookies.
    Affected if Cookies are transmitted over HTTP without the 'Secure' flag set.

If the device is one of the affected SIMATIC models, has its web server enabled, allows HTTP access, and transmits cookies without the Secure attribute over cleartext HTTP, the environment is vulnerable to CVE-2016-8672.

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

Update affected devices to the specified minimum versions (CP 343-1 Advanced: V3.0.53, CP 443-1 Advanced: V3.2.17, S7-300/400: consult Siemens for available patches). Alternatively, ensure all web server access occurs exclusively over HTTPS to mitigate cleartext cookie exposure.

Fix this in Simatic Cp 343 1 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing4.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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