CVE-2019-12917
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 XSS vulnerability exists in Quest KACE Systems Management Appliance Server Center 9.1.317 affecting the userui/software_library.php component via the PATH_INFO.
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 XSS vulnerability in Quest KACE SMA 9.1.317 allows attackers to inject malicious JavaScript via the PATH_INFO parameter in the userui/software_library.php component. The unsanitized user input is reflected back in the HTTP response, enabling session hijacking or credential theft.
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= 9.1.317CVSS 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 Quest KACE SMA installed versionAccess the KACE SMA administrative interface and navigate to the version information page, typically found under Settings > Appliance Settings > Version Info. Alternatively, check the login page footer or use the /api/info/version API endpoint if available.Affected if The displayed version number is exactly 9.1.317
-
Confirm software_library.php existsLocate the userui directory in the KACE SMA web root and verify that software_library.php is present. This file is typically found in the /userui/ path of the appliance's web directory structure.Affected if The file userui/software_library.php exists on the appliance
-
Verify PATH_INFO parameter reflectionSend an HTTP request to the software_library.php endpoint with a test payload in the PATH_INFO parameter, such as /userui/software_library.php/<script>alert(1)</script>. Inspect the HTTP response to see if the payload is reflected back without sanitization or encoding.Affected if The PATH_INFO parameter value is reflected verbatim in the response without HTML encoding or sanitization
-
Check for recent unauthorized accessReview KACE SMA access logs and authentication records for any suspicious requests targeting the software_library.php endpoint with unusual PATH_INFO parameters or unexpected JavaScript content.Affected if Logs show requests with malicious script tags or XSS payloads in the PATH_INFO to software_library.php
You are affected if your Quest KACE SMA version is exactly 9.1.317 and the userui/software_library.php component reflects PATH_INFO parameters without sanitization in HTTP responses.
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 strict input validation and context-aware output encoding for all user-supplied input in software_library.php, particularly PATH_INFO parameters.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12917 — 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-12917 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