Cloudforms 3.1 Management EngineApplication · Redhat
CVE-2014-7814
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 · uneditedSQL injection vulnerability in Red Hat CloudForms 3.1 Management Engine (CFME) 5.3 allows remote authenticated users to execute arbitrary SQL commands via a crafted REST API request to an SQL filter.
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 confidenceSQL injection vulnerability in Red Hat CloudForms 3.1 Management Engine 5.3 allows remote authenticated users to execute arbitrary SQL commands via a crafted REST API request containing malicious input to an SQL filter parameter.
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
Cloudforms 3.1 Management EngineApplication
= 5.3CVSS 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
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 CloudForms installationLocate the CloudForms Management Engine installation and retrieve its version number, typically found in the product's about or version information page in the web interface, or via command line tools provided by the productAffected if The installed version is exactly 5.3 of Red Hat CloudForms 3.1 Management Engine
-
Confirm REST API is accessibleVerify that the REST API endpoint is enabled and accessible on the CloudForms server, typically at /api or /rest/api pathAffected if The REST API interface is enabled and reachable without additional authentication barriers beyond the login requirement
-
Check for SQL filter parameter usageReview any custom or third-party integrations that make REST API calls using filter parameters, look for API requests that include filter= or similar query parameters passed to the REST APIAffected if Any REST API requests with filter parameters are being made to the vulnerable endpoint
-
Verify authentication methodDetermine if user accounts exist that can authenticate to the CloudForms REST API, as the vulnerability requires an authenticated sessionAffected if There are active user accounts with REST API access credentials
Your environment is affected only if you are running exactly Red Hat CloudForms 3.1 Management Engine version 5.3 with the REST API enabled and accessible to authenticated users who can submit filter parameters in API requests.
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 dataUpgrade to a patched version of CloudForms that addresses this vulnerability, or implement proper input validation and parameterized queries in the REST API filter handling code.
Fix this in Cloudforms 3.1 Management Engine
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7814 — 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-2014-7814 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