Cloudforms 3.0 Management EngineApplication · Redhat
CVE-2014-0137
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 the saved_report_delete action in the ReportController in Red Hat CloudForms Management Engine (CFME) before 5.2.3.2 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors, related to MiqReportResult.exists.
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 in the saved_report_delete action of Red Hat CloudForms Management Engine's ReportController allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors. The vulnerability is associated with the MiqReportResult.exists method, indicating the application fails to properly sanitize input before using it in a database query.
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.0 Management EngineApplication
<= 5.2.3= 5.2= 5.2.1= 5.2.2CVSS 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 if Red Hat CloudForms Management Engine is installedLook for the CloudForms Management Engine installation. Common locations include /var/www/miq/vmdb or check for the presence of the 'vmdb' directory. The application typically runs as a Ruby on Rails application.Affected if The product is not installed - if CloudForms is not present, this CVE does not apply.
-
Determine the installed version of CloudForms Management EngineCheck the version file typically found at /var/www/miq/vmdb/VERSION or run 'cat /var/www/miq/vmdb/VERSION' if the standard installation path exists. Alternatively, check the About page in the CloudForms web interface.Affected if The version is 5.2, 5.2.1, 5.2.2, or any version <= 5.2.3. If the version is 5.2.3.2 or later, the system is not affected by this specific CVE.
-
Verify the saved_report_delete functionality is accessibleConfirm that the ReportController's saved_report_delete action is enabled. This action is typically accessed via the web interface under the Reports section. Check if the /reports/saved_report_delete URL endpoint responds.Affected if The vulnerability requires authenticated access to the saved_report_delete action. If this functionality is not accessible or has been removed, the exploit cannot be triggered.
-
Inspect MiqReportResult.exists method usage in ReportControllerReview the Ruby code in the ReportController for the saved_report_delete action. Look for calls to MiqReportResult.exists? method where user-supplied parameters are passed directly to the database query without proper sanitization.Affected if The code uses MiqReportResult.exists with unsanitized user input from the saved_report_delete parameters. This indicates the vulnerable code path is present.
A system is affected if it runs Red Hat CloudForms Management Engine versions 5.2 through 5.2.3 (inclusive) and has the saved_report_delete functionality accessible to authenticated users with the vulnerable MiqReportResult.exists call present in the code.
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 CloudForms Management Engine version 5.2.3.2 or later. If immediate patching is not possible, restrict access to the saved_report_delete functionality to only trusted users and implement additional input validation at the application layer.
Fix this in Cloudforms 3.0 Management Engine
Scoped from the published advisory
- 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-2014-0137 — 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-0137 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