CVE-2019-12918
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 · uneditedQuest KACE Systems Management Appliance Server Center version 9.1.317 is vulnerable to SQL injection. The affected file is software_library.php and affected parameters are order[0][column] and order[0][dir].
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 confidenceQuest KACE Systems Management Appliance version 9.1.317 contains a critical SQL injection vulnerability in software_library.php via the order[0][column] and order[0][dir] parameters. These parameters, used for table ordering functionality, do not properly sanitize user input before incorporating it into SQL queries, allowing remote attackers to inject arbitrary SQL commands.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm Quest KACE SMA installation and versionAccess the KACE admin console login page or check system information. The version is typically displayed on the login page footer or in System Settings > Appliance Settings > Version. Alternatively, check the header of any API response from the SMA.Affected if The installed version is exactly 9.1.317
-
Verify software_library.php existsAccess the KACE SMA web directory and confirm software_library.php is present. This file is typically located in /admin/software_library.php or /kss/handlers/software_library.php depending on the installation path.Affected if The file software_library.php exists in the KACE web directory and the SMA version is 9.1.317
-
Confirm web interface is accessibleAttempt to access the KACE Systems Management Appliance login page or API endpoint over HTTP/HTTPS. The vulnerability requires the web application to be reachable.Affected if The KACE SMA web interface is accessible and the version is 9.1.317
-
Identify table ordering functionalityLog into the KACE admin console and navigate to the Software Library section. Look for any sortable table columns where ordering can be applied. The vulnerable parameters order[0][column] and order[0][dir] are used by the DataTables jQuery plugin for server-side table ordering.Affected if The Software Library page with sortable tables is accessible and the SMA version is 9.1.317
The environment is affected if Quest KACE Systems Management Appliance version 9.1.317 is installed and the Software Library web interface is accessible, since the SQL injection vulnerability exists in the table ordering parameters of software_library.php.
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 vendor patch or upgrade to a fixed version. If no patch available, implement WAF rules to block malicious order[0][column] and order[0][dir] input patterns, or modify the application code to use parameterized queries for all ORDER BY clauses.
- 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-12918 — 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-12918 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