CVE-2018-17928
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 product CMS-770 (Software Versions 1.7.1 and prior)is vulnerable that an attacker can read sensitive configuration files by bypassing the user authentication mechanism.
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 CMS-770 product versions 1.7.1 and prior contain an authentication bypass vulnerability that allows unauthenticated attackers to access sensitive configuration files. This is a direct authentication bypass leading to information disclosure of potentially credentials, database settings, API keys, and other secrets stored in configuration files.
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.7.1CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/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 the device as ABB CMS-770Check the product model number on the device label or access the device's web interface/system information page to confirm the model is CMS-770Affected if The device is not an ABB CMS-770 product
-
Determine the firmware versionAccess the device's admin interface or system settings page, or check the firmware file embedded in the device, and note the exact firmware version numberAffected if The firmware version is 1.7.1 or any version prior to 1.7.1
-
Verify if unauthenticated access to configuration files is possibleAttempt to access known configuration file paths or endpoints (such as /config, /settings, or similar paths that store configuration data) without providing any login credentialsAffected if Configuration files or sensitive settings are accessible without authentication credentials
-
Check for sensitive files in web-accessible directoriesUse a web browser or HTTP tool to probe the device for publicly accessible configuration, database, or credential storage files without being logged inAffected if Files containing credentials, API keys, or database settings are reachable without valid authentication
If the device is an ABB CMS-770 with firmware version 1.7.1 or lower and configuration files are accessible without authentication, the environment is affected by this CVE.
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 authentication checks on all sensitive endpoints and ensure configuration files are not accessible without valid authentication. Consider adding role-based access controls and verifying session handling mechanisms.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,024.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17928 — 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-17928 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