dbcve.org
CloudformsApplication · Redhat

CVE-2016-5383

HIGH · 8.8 CVSS v3.0 Published 2016-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
The web UI in Red Hat CloudForms 4.1 allows remote authenticated users to execute arbitrary code via vectors involving "Lack of field filters."

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 confidence

Red Hat CloudForms 4.1 web UI contains a code injection vulnerability where authenticated users can execute arbitrary code through input fields lacking proper filtering/sanitization. The 'Lack of field filters' allows malicious input in web form fields to be processed as executable code on the server.

MitigationApply vendor patches for Red Hat CloudForms 4.1 to address the field filter vulnerability. As an interim control, restrict access to the web UI to only trusted users and networks, and implement web application firewall rules to detect and block malicious input patterns.

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
Affected:= 4.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify CloudForms version
    Check the installed Red Hat CloudForms version. On the appliance console, use: `grep -i version /var/www/miq/vmdb/VERSION` or check the About page in the web UI under Help > About. Alternatively, run: `cat /etc/redhat-release` and look for CloudForms 4.1.
    Affected if The installed version is exactly 4.1 (version 4.1 matches the affected range)
  2. Confirm web UI is enabled
    Verify the web UI service is running. Check with: `systemctl status evmserverd` or `systemctl status httpd`. Also confirm port 443 or 80 is listening with: `netstat -tlnp | grep -E ':(80|443)'`
    Affected if The web UI service is active and accessible (the vulnerability only applies when the web interface is available)
  3. Identify accessible web form input fields
    Log into the CloudForms web UI as an authenticated user. Navigate to sections that accept user input such as: VM provisioning forms, custom button definitions, or automation scripts (Automate > Explorer). These are the form fields that lack proper filtering.
    Affected if You can access form fields in the web UI that accept user-supplied input without visible server-side sanitization (the flaw exists in these fields)
  4. Test for code injection in form fields
    As a test (in a non-production environment), inject a benign expression into a web form field (e.g., a custom button or automation input field) such as `<%= 1+1 %>` or `#{`id`}`. If the server executes this rather than treating it as literal text, the vulnerability is present.
    Affected if Input in web form fields is processed as executable code rather than treated as plain text (the field filter vulnerability is active)

You are affected if CloudForms version is exactly 4.1 AND the web UI is accessible AND web form fields execute injected input as code instead of treating it as plain text.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for Red Hat CloudForms 4.1 to address the field filter vulnerability. As an interim control, restrict access to the web UI to only trusted users and networks, and implement web application firewall rules to detect and block malicious input patterns.

Fix this in Cloudforms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-5383 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-5383 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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