Enterprise LinuxOperating system · Redhat
CVE-2019-10221
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 Reflected Cross Site Scripting vulnerability was found in all pki-core 10.x.x versions, where the pki-ca module from the pki-core server. This flaw is caused by missing sanitization of the GET URL parameters. An attacker could abuse this flaw to trick an authenticated user into clicking a specially crafted link which can execute arbitrary code when viewed in a browser.
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 confidenceA reflected Cross Site Scripting (XSS) vulnerability exists in the pki-ca module of pki-core versions 10.x.x. The flaw is caused by missing sanitization of GET URL parameters, allowing an attacker to inject malicious scripts through specially crafted URLs.
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
Enterprise LinuxOperating system
= 7.0= 8.0>= 10.0, <= 10.8.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
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Verify pki-ca module is installedCheck if the pki-ca or dogtag-pki-ca package is installed on the system using the package manager (e.g., rpm -qa | grep -i 'pki-ca\|dogtag.*ca' or dpkg -l | grep -i pki-ca)Affected if The pki-ca package is found installed on the system
-
Determine pki-core versionRun 'rpm -q pki-core' or check the installed version of the pki-core package to identify the exact version numberAffected if The installed pki-core version is 10.x.x (between 10.0 and 10.8.3 inclusive) or matches Red Hat Enterprise Linux 7.0 or 8.0 PKI versions
-
Confirm pki-ca web interface is accessibleCheck if the pki-ca web service is running and accessible (typically at /ca or /pki/ca endpoints on the system's HTTP/HTTPS port)Affected if The pki-ca web interface is exposed and accepts user-supplied URL parameters
-
Test for reflected XSS in URL parametersAccess the pki-ca endpoint with a test parameter in the URL (e.g., https://<host>/ca/<parameter>=<script>alert(1)</script>) and observe if the script content is reflected back in the response without encodingAffected if The pki-ca module reflects unsanitized URL parameter values directly in HTML output, causing the injected script to execute in the browser
A system is affected if it runs pki-core version 10.0 through 10.8.3 (or RHEL 7.0/8.0 PKI) with the pki-ca module accessible via web, and URLs with unsanitized parameters reflect back script content.
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 dataApply available patches for pki-core to address the input validation vulnerability, and implement output encoding for user-supplied URL parameters in the pki-ca module.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2019-10221 — 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-10221 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