CVE-2017-7906
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 · uneditedIn ABB IP GATEWAY 3.39 and prior, the web server does not sufficiently verify that a request was performed by the authenticated user, which may allow an attacker to launch a request impersonating that user.
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 confidenceThis is a request forgery vulnerability in ABB IP GATEWAY's web server (v3.39 and prior) where the server fails to adequately verify that incoming requests originate from the authenticated user. An attacker could craft malicious requests that the server accepts as if coming from a legitimate authenticated user, enabling unauthorized actions.
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<= 3.39CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 device as ABB IP GatewayAccess the web interface or check the device firmware documentation to confirm the product is ABB IP Gateway. This vulnerability only affects this specific product.Affected if The device is not an ABB IP Gateway product.
-
Determine the firmware versionLog into the ABB IP Gateway web interface and navigate to the system information or firmware version page. Alternatively, check the firmware file or device label.Affected if The installed firmware version is 3.39 or lower.
-
Verify the web server is accessibleConfirm the ABB IP Gateway web interface is reachable over HTTP/HTTPS on the network. The vulnerability exists in the web server component.Affected if The web server is accessible and serves the ABB IP Gateway interface.
-
Check for anti-CSRF protection mechanismsInspect the web application's HTML forms and AJAX requests for the presence of anti-CSRF tokens. Submit a sensitive request (such as a configuration change) and verify that the server validates a unique token tied to the user session.Affected if The web application lacks anti-CSRF tokens in forms and does not validate the Origin or Referer headers for incoming requests.
A user is affected if they have an ABB IP Gateway device running firmware version 3.39 or lower with its web interface accessible and without proper anti-CSRF protections in place.
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 proper request validation mechanisms such as anti-CSRF tokens, origin/header verification, or re-authentication for sensitive operations. Upgrade to a patched version if available from ABB.
- 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-7906 — 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-7906 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