Cloudforms Management EngineApplication · Redhat
CVE-2019-10177
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 stored cross-site scripting (XSS) vulnerability was found in the PDF export component of CloudForms, versions 5.9 and 5.10, due to user input is not properly sanitized. An attacker with least privilege to edit compute is able to execute a XSS attack against other users, which could lead to malicious code execution and extraction of the anti-CSRF token of higher privileged users.
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 confidenceStored cross-site scripting (XSS) vulnerability in the PDF export component of CloudForms versions 5.9 and 5.10. User-supplied input in compute/VM fields is not sanitized before being embedded in exported PDFs, allowing attackers with low-privilege compute edit access to inject malicious scripts that execute in browsers of users viewing the exported PDFs.
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.9= 5.10CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
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 installation and versionCheck the installed version of Red Hat CloudForms Management Engine. This is typically visible in the product UI under the About section, or via the appliance console. Compare the version to 5.9 or 5.10.Affected if The installed version is 5.9 or 5.10 exactly.
-
Verify PDF export functionality is accessibleConfirm that the PDF export feature is available in the environment. This feature is typically found in the CloudForms UI under VM details, reports, or infrastructure views where PDF generation options exist.Affected if PDF export functionality is present and accessible to users.
-
Check for compute edit access permissionsReview user roles and permissions to determine if any users have low-privilege compute edit access. This can be done by examining the access control configuration in CloudForms under Configuration -> Access Control.Affected if Users have compute edit access permissions, even at low privilege levels.
-
Inspect VM and compute field names for potential XSS payloadsReview all VM names and compute field entries in the CloudForms database or UI. Look for any unexpected characters or patterns that could indicate injected script tags (such as <script>, javascript:, or HTML tags) in VM names or custom fields.Affected if Any VM names or compute fields contain unsanitized user input that includes script tags or XSS vectors.
The environment is affected if CloudForms version is exactly 5.9 or 5.10, the PDF export feature is accessible, and users with compute edit access can create or modify VM fields containing unsanitized input that would be rendered in exported PDFs.
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 dataSanitize all user input in the PDF export component before embedding in output; implement context-aware output encoding and considerContent Security Policy headers to mitigate XSS risks.
Fix this in Cloudforms Management Engine
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10177 — 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-2019-10177 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