Cloudforms Management EngineApplication · Redhat
CVE-2017-2653
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 number of unused delete routes are present in CloudForms before 5.7.2.1 which can be accessed via GET requests instead of just POST requests. This could allow an attacker to bypass the protect_from_forgery XSRF protection causing the routes to be used. This attack would require additional cross-site scripting or similar attacks in order to execute.
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 confidenceCloudForms before 5.7.2.1 contains unused DELETE routes that accept GET requests instead of being restricted to POST only. This bypasses Rails' protect_from_forgery CSRF protection mechanism, enabling attackers to trigger delete operations via GET requests. Exploitation requires an accompanying XSS or similar attack to actually invoke the malicious requests.
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 Management EngineApplication
< 5.7.2.1
CloudformsApplication
= 4.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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 installed CloudForms versionAccess the CloudForms management interface and navigate to About page, or run 'docker ps' or 'rpm -q cfme' to find the installed versionAffected if Version is below 5.7.2.1 or is exactly 4.2
-
Examine Rails route configurationInspect the Rails routes.rb file (typically in /var/www/miq/vmdb/config/routes.rb or similar path) and look for delete route definitionsAffected if DELETE routes include 'via: [:get]' or lack explicit restriction to POST only
-
Check application configuration for CSRF settingsLook at the application controller (application_controller.rb) and verify the protect_from_forgery configuration allows GET requests to delete actionsAffected if protect_from_forgery is not properly enforced or DELETE actions accept GET method without CSRF token validation
-
Verify HTTP method enforcement on delete endpointsTest a known delete endpoint (such as /api/providers/:id or similar) with a GET request to confirm it is acceptedAffected if GET requests to delete endpoints return a successful response instead of being rejected (405 Method Not Allowed)
-
Review web server configurationCheck nginx/apache configuration in front of CloudForms for any method restrictions on delete pathsAffected if No WAF or load balancer rules block GET requests to delete endpoints
A system is affected if it runs CloudForms version 4.2 or any version below 5.7.2.1 and allows GET requests to trigger DELETE operations, bypassing Rails CSRF protection.
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 data5.7.2.1
Upgrade to CloudForms 5.7.2.1 or later which properly restricts DELETE routes to POST requests only, or implement WAF/load balancer rules to block GET requests to delete endpoints.
Fix this in Cloudforms Management Engine
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2653 — 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-2017-2653 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