CVE-2017-5165
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. There is no CSRF Token generated per page and/or per (sensitive) function. Successful exploitation of this vulnerability can allow silent execution of unauthorized actions on the device such as configuration parameter changes, and saving modified configuration.
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 confidenceThe BINOM3 Electric Power Quality Meter web interface lacks anti-CSRF tokens, allowing attackers to craft malicious requests that execute silently when a logged-in user visits a malicious site. Since the device accepts requests without validating token authenticity, an attacker can trigger unauthorized configuration changes.
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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm Binom3 device is present on the networkAccess the web interface of the Binom3 Universal Multifunctional Electric Power Quality Meter by navigating to its IP address in a web browser. Verify the device model and firmware version are displayed in the interface header or system information page.Affected if The device is accessible and identifies as a Binom3 Electric Power Quality Meter with any firmware version.
-
Locate configuration-related forms in the web interfaceNavigate to the settings or configuration sections of the web interface where users can modify device parameters (network settings, meter configuration, user management). Identify all HTML forms that perform state-changing operations.Affected if The web interface contains forms for making configuration changes.
-
Inspect HTML source for anti-CSRF tokensRight-click on configuration forms and select 'View Page Source' or use browser developer tools to examine the HTML. Look for hidden input fields with names containing 'token', 'csrf', 'nonce', or similar security tokens within the form tags.Affected if No hidden anti-CSRF token fields are present in the HTML of configuration forms.
-
Check form submission behaviorSubmit a configuration change through the web interface and observe the HTTP request using browser developer tools (Network tab). Examine whether the request includes any token parameters beyond standard form fields.Affected if The form submission HTTP POST request contains no token, nonce, or CSRF-specific parameter.
-
Verify server-side token validationCompare the behavior when submitting the same configuration change with and without a fabricated token parameter. If the server accepts both requests without rejecting the invalid token, no server-side validation occurs.Affected if The server processes configuration requests regardless of token validity, indicating no server-side CSRF protection.
You are affected if you have a Binom3 Electric Power Quality Meter with its web interface accessible and the configuration forms lack anti-CSRF tokens in their HTML.
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 per-session or per-request CSRF tokens for all sensitive functions (configuration changes, settings save). Validate tokens server-side before processing any state-changing request.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5165 — 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-5165 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