CVE-2017-7914
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 Missing Authorization issue was discovered in Rockwell Automation PanelView Plus 6 700-1500 6.00.04, 6.00.05, 6.00.42, 6.00-20140306, 6.10.20121012, 6.10-20140122, 7.00-20121012, 7.00-20130108, 7.00-20130325, 7.00-20130619, 7.00-20140128, 7.00-20140310, 7.00-20140429, 7.00-20140621, 7.00-20140729, 7.00-20141022, 8.00-20140730, and 8.00-20141023. There is no authorization check when connecting to the device, allowing an attacker remote access.
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 missing authorization check in Rockwell Automation PanelView Plus 6 (firmware versions 6.00.04 through 8.00-20141023) allows unauthenticated remote attackers to connect to the device without any credentials, granting full access to the HMI interface and potentially the connected control system.
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= 6.00-20140306= 6.00.04= 6.00.05= 6.00.42= 6.10-20140122= 6.10.20121012= 7.00-20121012= 7.00-20130108= 7.00-20130325= 7.00-20130619= 7.00-20140128= 7.00-20140310CVSS 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
- Low
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
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 the PanelView Plus modelLocate the device nameplate or access the device info screen on the HMI. Confirm the model is PanelView Plus 6, specifically the 700 or 1500 variant.Affected if The device is not a PanelView Plus 6 (700 or 1500)
-
Determine the installed firmware versionAccess the device through the built-in web server or via the HMI System Information screen. Look for the firmware version string in the format shown (e.g., 6.00.04, 7.00-20130325).Affected if The firmware version matches one of these: 6.00-20140306, 6.00.04, 6.00.05, 6.00.42, 6.10-20140122, 6.10.20121012, 7.00-20121012, 7.00-20130108, 7.00-20130325, 7.00-20130619, 7.00-20140128, 7.00-20140310, or any version in the range 6.00.04 through 8.00-20141023
-
Verify if the built-in web server is enabledAccess the device Configuration mode and navigate to the Communications or Network settings. Check if the embedded web server is turned on and accessible over the network.Affected if The web server is enabled and reachable from the network
-
Confirm whether the device is network-accessible from outside the local control systemReview network firewall rules, VLAN configuration, and any port forwarding or DMZ setups. Check if the device HTTP ports (typically 80/443) are exposed to untrusted networks.Affected if The device can be reached from networks beyond the isolated control system environment
You are affected if you have a PanelView Plus 6 (700 or 1500) running any firmware version between 6.00.04 and 8.00-20141023, with the web server enabled and the device accessible from a network where unauthenticated attackers could reach it.
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 firmware patches when available; if no patch exists, isolate affected devices behind network segmentation and firewalls to prevent unauthorized external access, and disable remote connectivity if not operationally required.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7914 — 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-7914 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