CVE-2016-4367
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 Universal Discovery component in HPE Universal CMDB 10.0, 10.01, 10.10, 10.11, 10.20, and 10.21 allows remote attackers to obtain sensitive information via unspecified vectors.
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 confidenceCVE-2016-4367 is an information disclosure vulnerability in the Universal Discovery component of HPE Universal CMDB versions 10.0 through 10.21. The vulnerability allows remote unauthenticated attackers to obtain sensitive information via unspecified vectors, indicating a potential lack of proper access controls or input validation in the discovery service.
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.0= 10.01= 10.10= 10.11= 10.20= 10.21CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/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 HPE Universal CMDB Foundation installationLocate and verify the HPE Universal CMDB Foundation product is installed in your environment. This may be found in installed software listings, application inventories, or system documentation.Affected if The product HPE Universal CMDB Foundation is present
-
Determine the installed versionUse the system's software inventory, version lookup command, or administrative console to identify the exact version number of the Universal CMDB Foundation installation.Affected if The version matches 10.0, 10.01, 10.10, 10.11, 10.20, or 10.21
-
Confirm the Universal Discovery component is in useCheck if the Universal Discovery component is enabled or deployed within the Universal CMDB installation. Review component listings, service configurations, or administrative interfaces.Affected if Universal Discovery component is enabled or deployed
-
Assess network exposure of the discovery serviceReview network configurations, firewall rules, or access control lists to determine if the Universal Discovery service is accessible from network locations, particularly external or untrusted networks.Affected if The discovery component is exposed to untrusted networks or accessible without authentication
-
Inspect discovery service access logsExamine logs from the Universal Discovery component for any access from unauthenticated or unexpected sources, unusual query patterns, or attempts to access sensitive discovery data.Affected if Logs show unauthorized access attempts or unexpected information disclosures
You are affected if HPE Universal CMDB Foundation versions 10.0 through 10.21 is installed with the Universal Discovery component enabled and exposed to network access.
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 the HPE security patch for this vulnerability; if unavailable, restrict network access to the Universal Discovery component and audit the component's access logs for indicators of compromise.
- Consultation2.0 h
- Implementation4.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 $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4367 — 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-2016-4367 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