CloudformsApplication · Redhat
CVE-2016-5402
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 · uneditedA code injection flaw was found in the way capacity and utilization imported control files are processed. A remote, authenticated attacker with access to the capacity and utilization feature could use this flaw to execute arbitrary code as the user CFME runs as.
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 confidenceA code injection vulnerability exists in the capacity and utilization feature of Red Hat CloudForms (CFME) when importing control files. A remote, authenticated attacker can inject and execute arbitrary code with the privileges of the CFME service user by submitting specially crafted control files through the import functionality.
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
CloudformsApplication
= 4.1
Cloudforms Management EngineApplication
= 5.6CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Identify the installed CloudForms versionRun 'rhsmctl status' or check /var/www/miq/vmdb/VERSION file, or access the UI: Help > About to confirm the exact version numberAffected if Version is exactly 4.1 (CloudForms) or exactly 5.6 (CFME)
-
Confirm the capacity and utilization feature is enabledNavigate to CloudForms UI: Configure > Configuration > Settings > C&U Collection and verify capacity and utilization collection is turned on, or check the database table miq_cim_configurationAffected if Capacity and utilization collection is enabled in the appliance settings
-
Verify the import functionality is accessibleCheck if the /capacity_utilization/import endpoint is reachable or inspect the appliance for the import control file capability in the C&U settings UIAffected if The capacity and utilization import feature is exposed and accessible to authenticated users
-
Review user access controls for the import functionExamine the role-based access control settings for authenticated users: Configure > Configuration > Access Control > Roles and check if users have Import or Operations privileges on the C&U featureAffected if Authenticated users have Import or similar privileges on capacity and utilization features
A system is affected if it runs CloudForms 4.1 or CFME 5.6, has capacity and utilization enabled, and has the import functionality accessible to authenticated users.
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 vendor patch for CVE-2016-5402. As an interim measure, disable or severely restrict access to the capacity and utilization import functionality until the patch can be deployed.
Fix this in Cloudforms
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5402 — 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-5402 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