CVE-2017-5164
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 · uneditedAn issue was discovered in BINOM3 Universal Multifunctional Electric Power Quality Meter. Input sent from a malicious client is not properly verified by the server. An attacker can execute arbitrary script code in another user's browser session (CROSS-SITE SCRIPTING).
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 confidenceCross-site scripting (XSS) vulnerability in the BINOM3 Universal Multifunctional Electric Power Quality Meter web interface. The server fails to properly validate input from clients, allowing an attacker to inject malicious script code that executes in another user's browser session.
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 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Confirm the device modelAccess the device or its management interface and identify if it is a Binom3 Universal Multifunctional Electric Power Quality Meter. This may be visible on the device label, in the device documentation, or via SNMP/network discovery.Affected if The device is a Binom3 Universal Multifunctional Electric Power Quality Meter.
-
Check if the web interface is enabledDetermine whether the web-based management interface is enabled on the device. This may be configurable in the device settings, or by attempting to access the default HTTP/HTTPS ports (commonly 80/443 or vendor-specific ports) on the device IP address.Affected if The web interface is accessible and operational on the network.
-
Verify firmware versionIf the web interface is accessible, navigate to the firmware or system information page within the web application to retrieve the installed firmware version number.Affected if The firmware version is any version of the Binom3 Universal Multifunctional Electric Power Quality Meter (all versions are affected).
-
Test for reflected input without sanitizationUsing an authorized testing methodology, submit a benign script payload (such as <script>alert('test')</script>) into input fields within the web interface (for example, in parameter fields, labels, or configuration inputs) and observe whether the payload is reflected and executed in the response without encoding or sanitization.Affected if The submitted script content is returned verbatim in the HTML response and executes in the browser.
The environment is affected if the device is a Binom3 Universal Multifunctional Electric Power Quality Meter with its web interface enabled, regardless of firmware 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 dataImplement server-side input validation and output encoding to sanitize user-supplied data before storage and display. This likely requires a firmware update from the vendor that adds proper input sanitization routines to the web application.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5164 — 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-5164 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