CVE-2017-6873
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 · uneditedA vulnerability was discovered in Siemens OZW672 (all versions) and OZW772 (all versions) that could allow an attacker to read and manipulate data in TLS sessions while performing a man-in-the-middle (MITM) attack on the integrated web server on port 443/tcp.
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 confidenceA vulnerability in Siemens OZW672 and OZW772 web servers on port 443/tcp allows attackers to perform MITM attacks, enabling them to read and manipulate data in TLS sessions. This indicates a fundamental flaw in TLS certificate validation or cipher suite implementation.
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 dataall 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify OZW672 or OZW772 instances on the networkScan your network for devices running Siemens OZW672 or OZW772 web servers. Check for devices responding on port 443/tcp with HTTP(s) headers indicating these products. Use network scans or review device inventories.Affected if OZW672 or OZW772 devices with port 443/tcp accessible on your network are affected since all firmware versions contain the vulnerability
-
Verify port 443/tcp exposureCheck if port 443/tcp is open and reachable on OZW672/OZW772 devices. Use port scanning tools (nmap -p 443 <target>) or review firewall rules and network segmentation configurations.Affected if Any OZW672 or OZW772 device with port 443/tcp exposed to network traffic is vulnerable to MITM attacks
-
Confirm TLS session behaviorAttempt to connect to the web server on port 443/tcp and inspect TLS handshake details. Use tools like openssl s_client -connect <host>:443 or sslyze to examine certificate validation and cipher suites.Affected if If the device accepts connections without proper certificate validation or uses weak cipher suites, it is vulnerable to the MITM flaw described in this CVE
-
Review TLS configuration for certificate validation gapsAnalyze the TLS implementation on the OZW672/OZW772 web server. Check if certificate chain validation, hostname verification, or certificate revocation checks are missing or can be bypassed.Affected if If certificate validation is missing or can be bypassed, the TLS sessions are susceptible to interception and manipulation
You are affected if you have any Siemens OZW672 or OZW772 devices with port 443/tcp accessible on your network, regardless of firmware version, as all versions contain the TLS certificate validation flaw enabling MITM attacks.
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 dataApply vendor-supplied patches or firmware updates for OZW672 and OZW772. Until patched, restrict network access to port 443/tcp and monitor for MITM attack indicators.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6873 — 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-2017-6873 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