CVE-2022-29807
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 SQL injection vulnerability exists within Quest KACE Systems Management Appliance (SMA) through 12.0 that can allow for remote code execution via download_agent_installer.php.
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 SQL injection vulnerability exists in Quest KACE Systems Management Appliance (SMA) through version 12.0 within the download_agent_installer.php component. Attackers can inject malicious SQL queries through this vector, which can lead to remote code execution on the affected appliance.
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< 12.1.168CVSS 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.
-
Identify if Quest KACE SMA is installedCheck for the KACE SMA web interface by accessing the management URL (typically /api) or look for 'KACE' or 'Quest' in the server HTTP headers. On the appliance itself, check for the 'kbox' service running.Affected if The system is running Quest KACE Systems Management Appliance
-
Determine the installed KACE SMA versionLog into the KACE SMA admin console and navigate to the System Settings page, or access the /api/version endpoint if available. Alternatively, check the appliance's about page or run 'sudo /opt/dell/kace/bin/component.sh -v' if SSH access is available.Affected if The installed version is below 12.1.168 (for example, 12.0.x, 11.x, or earlier)
-
Check if the vulnerable download_agent_installer.php component is presentAttempt to access the file directly via HTTP: GET /download_agent_installer.php. If the file exists and is accessible, the server will respond (even if authentication is required).Affected if The download_agent_installer.php file exists and returns a valid HTTP response
-
Verify network exposure of the SMA management interfaceDetermine if the KACE SMA web interface is accessible from untrusted networks. Check firewall rules, NAT configurations, or reverse proxy settings that expose the SMA login page to the internet or dmz.Affected if The SMA management interface is accessible from outside the trusted network without proper access controls
A system is affected if it runs Quest KACE SMA version 12.0 or any version below 12.1.168 with the download_agent_installer.php component accessible to potential attackers.
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.
dbcve · scoped12.1.168
Apply the vendor-provided patch for KACE SMA version 12.0 or later. If immediate patching is not feasible, implement network segmentation or firewall rules to restrict unauthorized access to the SMA management interface.
KACE Systems Management Appliance 12.1.168 or later
- Obtain the KACE Systems Management Appliance version 12.1.168 or later from the official Quest support portal at support.quest.com
- Review the upgrade documentation and release notes for version 12.1.168
- Ensure you have a complete backup of the current appliance configuration and data
- Schedule a maintenance window as the upgrade may require downtime
- Download the upgrade package from Quest's official support site
- Follow the documented upgrade procedure to apply version 12.1.168 to the affected KACE SMA
- Verify the upgrade was successful and the web interface is accessible
- Confirm the download_agent_installer.php endpoint is functioning correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29807 — 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-2022-29807 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