Enterprise LinuxOperating system · Redhat
CVE-2019-10179
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 vulnerability was found in all pki-core 10.x.x versions, where the Key Recovery Authority (KRA) Agent Service did not properly sanitize recovery request search page, enabling a Reflected Cross Site Scripting (XSS) vulnerability. An attacker could trick an authenticated victim into executing specially crafted Javascript code.
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 confidenceA reflected Cross Site Scripting (XSS) vulnerability exists in the Key Recovery Authority (KRA) Agent Service of pki-core 10.x.x. The recovery request search page fails to properly sanitize user input, allowing authenticated attackers to inject malicious JavaScript code through specially crafted URLs that get executed in the victim's browser.
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.
-
Identify if KRA Agent Service is installedCheck for the presence of the KRA agent web application. On Red Hat systems, look for /var/lib/pki/kra/ directory or query the installed packages: rpm -qa | grep -i pki-kraAffected if The KRA agent component is not installed on the system
-
Determine the installed pki-core or Dogtagpki versionRun 'rpm -q pki-core' on Red Hat systems or check the Dogtagpki version through the package manager: rpm -qa | grep dogtag-pkiAffected if The version falls outside the affected range (pki-core 10.x.x, Dogtagpki >= 10.0 <= 10.8.3, or RHEL 7.0/8.0)
-
Verify the KRA agent web interface is accessibleCheck if the KRA agent endpoint is accessible. Typically found at /kra/agent or /ca/ee/kra under the pki instance. Access the recovery request search page if the service is runningAffected if The KRA agent service is not exposed or not running
-
Inspect web server logs for signs of XSS exploitationReview access and error logs for the KRA agent application. Look for suspicious patterns in URL parameters, especially in recovery request search queries. Check /var/log/pki/<instance>/<date>.log or similar log locationsAffected if Evidence of malicious JavaScript in URL parameters targeting the recovery request search functionality
A system is affected if it runs Dogtagpki or pki-core version 10.0 through 10.8.3 on RHEL 7.0/8.0 with the KRA agent service enabled and accessible.
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 dataImplement proper input validation and output encoding on the recovery request search page, specifically sanitizing all user-supplied parameters before rendering them in HTML context.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10179 — 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-10179 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