CVE-2018-13991
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 · uneditedThe WebUI of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, 48xx versions 1.0 to 1.34 leaks private information in firmware images.
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 · moderate confidenceThe WebUI component of PHOENIX CONTACT FL SWITCH 3xxx, 4xxx, and 48xx series industrial network switches versions 1.0 through 1.34 contains an information disclosure vulnerability where private information is leaked within firmware images. This could allow an attacker with access to the firmware to extract sensitive data that was not intended to be exposed.
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>= 1.0, <= 1.34>= 1.0, <= 1.34>= 1.0, <= 1.34>= 1.0, <= 1.34>= 1.0, <= 1.34>= 1.0, <= 1.34>= 1.0, <= 1.34>= 1.0, <= 1.34CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the device WebUI or CLI and check the product model name. Look for FL SWITCH 3xxx series models (3005, 3005t, 3004t Fx, 3004t Fx St, 3008, 3008t, 3006t 2fx, 3006t 2fx St).Affected if The device model matches one of the listed affected models.
-
Check firmware versionIn the device WebUI, navigate to the System > Information or Status page to view the firmware version. Alternatively, use the CLI command 'show system' or similar to retrieve the firmware version.Affected if The displayed firmware version is between 1.0 and 1.34 inclusive.
-
Verify WebUI is accessibleAttempt to access the device WebUI over HTTP/HTTPS by entering the device IP address in a browser.Affected if The WebUI interface is reachable on the network.
-
Inspect firmware file (if available)If you have obtained a firmware update file, open it with a hex editor or strings command to search for sensitive data patterns such as passwords, keys, or private credentials that should not be publicly exposed.Affected if The firmware file contains private information that is not intended to be exposed.
A user is affected if they are running a Phoenix Contact FL SWITCH 3xxx series model with firmware version 1.0 through 1.34, and the device WebUI is accessible or they possess a firmware image from an affected version.
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 the device firmware to a version beyond 1.34 if a patched version is available, and implement network segmentation or firewall controls to restrict unauthorized access to the device WebUI interface.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13991 — 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-2018-13991 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