CVE-2019-18998
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 · uneditedInsufficient access control in the web interface of ABB Asset Suite versions 9.0 to 9.3, 9.4 prior to 9.4.2.6, 9.5 prior to 9.5.3.2 and 9.6.0 enables full access to directly referenced objects. An attacker with knowledge of a resource's URL can access the resource directly.
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 confidenceInsecure Direct Object Reference (IDOR) vulnerability in ABB Asset Suite web interface. The application fails to validate user authorization when accessing resources directly via URL, allowing authenticated or unauthenticated attackers to bypass access controls and view sensitive objects by knowing their URLs.
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>= 9.0.0, <= 9.3.0>= 9.4, < 9.4.2.6>= 9.5.0, < 9.5.3.2= 9.6.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Identify the installed Asset Suite versionLocate the version information in the application's about page, system information panel, or check the installation directory for version files. Use the product's administrative interface or built-in version command if available.Affected if The installed version falls within any of these ranges: 9.0.0 through 9.3.0, 9.4.0 through 9.4.2.5, 9.5.0 through 9.5.3.1, or equals 9.6.0
-
Confirm the web interface is accessibleVerify that the Asset Suite web interface is exposed and reachable on the network. Check if HTTP/HTTPS ports used by the application are open and responding.Affected if The web interface is accessible and the version from step 1 is within the affected ranges
-
Review access logs for direct object reference patternsExamine web server and application access logs for unusual GET requests to object URLs (such as /asset/*, /object/*, /document/*) that may indicate enumeration or unauthorized access attempts. Look for requests with sequential or guessable identifiers.Affected if Logs show direct URL access to sensitive objects by users who should not have authorization to those specific resources, especially if accompanied by unusual parameter patterns
You are affected if the installed Asset Suite version is one of the unpatched versions listed in step 1 and the web interface is accessible.
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 data9.4.2.69.5.3.2
Apply vendor patches (9.4.2.6, 9.5.3.2, or later) to implement proper authorization checks on all object references. Until patched, monitor access logs for suspicious direct URL access patterns.
- Consultation8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18998 — 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-2019-18998 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