dbcve.org
Kace Asset Management ApplianceApplication · Quest

CVE-2017-12567

CRITICAL · 9.8 CVSS v3.0 Published 2017-08-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
SQL injection exists in Quest KACE Asset Management Appliance 6.4.120822 through 7.2, Systems Management Appliance 6.4.120822 through 7.2.101, and K1000 as a Service 7.0 through 7.2.

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 confidence

SQL injection vulnerability in Quest KACE appliances (Asset Management, Systems Management, and K1000 as a Service) versions 6.4.120822-7.2/7.2.101 allows unauthenticated attackers to inject malicious SQL queries via unsanitized input, potentially enabling unauthorized data access, modification, or complete system compromise.

MitigationApply vendor-provided patches immediately; until then, restrict network access to the appliances and deploy a WAF with SQL injection rules. Conduct thorough code review to identify and remediate all unsanitized SQL input points.

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
Kace Asset Management ApplianceApplication
Affected:= 6.4.120822= 7.0= 7.0.121306= 7.1= 7.1.149= 7.2
Kace Systems Management ApplianceApplication
Affected:= 6.4.120822= 7.0= 7.0.121306= 7.1= 7.1.149= 7.2= 7.2.101
K1000 As A ServiceApplication
Affected:= 7.0= 7.0.121306= 7.1= 7.1.149= 7.2

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Quest KACE appliance type
    Determine which Quest KACE product is deployed: Asset Management Appliance, Systems Management Appliance, or K1000 as a Service. This is typically visible in the product name, licensing documentation, or the appliance admin interface.
    Affected if The product is one of these three variants and the version is unpatched.
  2. Determine the installed version
    Locate the version information in the appliance web interface (typically under Help > About or System > Settings > General) or check the login banner for version numbers. Compare against the affected version list: 6.4.120822, 7.0, 7.0.121306, 7.1, 7.1.149, 7.2, or 7.2.101.
    Affected if The installed version matches any of these specific versions.
  3. Verify network accessibility of the appliance
    Determine if the KACE appliance login page or API endpoints are reachable from untrusted networks. Check firewall rules, VPN policies, and whether the appliance is exposed directly to the internet.
    Affected if The appliance administrative interface is accessible without authentication from untrusted networks.
  4. Check for unauthorized access indicators
    Review appliance logs (under Reports > Logs or System > Logs) for unusual SQL syntax errors, unexpected database queries, or authentication failures from unfamiliar IP addresses. Monitor for data exfiltration patterns.
    Affected if Log entries show suspicious SQL-like queries or unauthorized database access attempts.

A user is affected if they run a Quest KACE Asset Management, Systems Management, or K1000 as a Service appliance version 6.4.120822 through 7.2.101 with the vulnerable interface exposed to network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches immediately; until then, restrict network access to the appliances and deploy a WAF with SQL injection rules. Conduct thorough code review to identify and remediate all unsanitized SQL input points.

Recommended fix Moderate confidence

KACE version 7.3 or later (specifically 7.3 for Asset Management Appliance and K1000 as a Service; 7.2.102 or later for Systems Management Appliance)

  1. 1. Back up the current KACE appliance configuration and any critical data before upgrading.
  2. 2. Log in to the KACE admin console as an administrator.
  3. 3. Navigate to the System Settings or Administration section.
  4. 4. Locate the firmware/software update or upgrade option.
  5. 5. Initiate an upgrade to version 7.3 or the latest available stable release.
  6. 6. Verify the upgrade completes successfully and the appliance restarts.
  7. 7. Confirm the SQL injection vulnerability is resolved by checking the Quest KACE release notes for version 7.3.
Caveat Standard upgrade risks apply - ensure backup before proceeding; test in non-production environment first if possible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kace Asset Management Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12567 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-12567 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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