CVE-2018-6491
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 · uneditedLocal Escalation of Privilege vulnerability to Micro Focus Universal CMDB, versions 10.20, 10.21, 10.22, 10.30, 10.31, 10.32, 10.33, 11.00. The vulnerability could be remotely exploited to Local Escalation of Privilege.
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 confidenceMicro Focus Universal CMDB versions 10.20 through 11.00 contain a vulnerability that can be remotely exploited to achieve local privilege escalation, allowing an attacker to gain elevated system privileges on the target host.
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= 10.20= 10.21= 10.22= 10.30= 10.31= 10.32= 10.33= 11.00CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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.
-
Verify Micro Focus UCMDB is installedCheck for UCMDB installation directories (typically under C:\Program Files\Micro Focus or /opt/microfocus) or look for the 'UCMDB' or 'Universal CMDB' service in Windows Services or Unix init/systemd listingsAffected if The product is not installed on the system
-
Determine installed UCMDB versionAccess the UCMDB Admin Console or check version files in the installation directory. In the admin UI, navigate to Help > About or check version.txt in the installation root. Alternatively, query the UCMDB server via its API or check the installer log filesAffected if The installed version matches 10.20, 10.21, 10.22, 10.30, 10.31, 10.32, 10.33, or 11.00 exactly
-
Confirm UCMDB server service is runningCheck if the UCMDB Server service (UCMDBServer or similar) is running. On Windows, use Services.msc or 'sc query UCMDB'. On Linux, use 'systemctl status ucmdb' or check for java processes related to UCMDBAffected if The vulnerable service is exposed and running, enabling remote exploitation
-
Check if remote access is enabledVerify that the UCMDB web interface or API endpoints are accessible from the network. Check firewall rules and the server.xml or wrapper.conf configuration for binding addresses. Look for open ports typically used by UCMDB (8080, 8443)Affected if The UCMDB web service is exposed to the network without proper network segmentation
The system is affected if Micro Focus Universal CMDB is installed and the installed version is exactly 10.20, 10.21, 10.22, 10.30, 10.31, 10.32, 10.33, or 11.00, with the service running and 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 dataApply available patches from Micro Focus for Universal CMDB or upgrade to a patched version. Given the critical CVSS score and remote exploitability, prioritize patching immediately.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6491 — 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-6491 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