CVE-2019-10973 json
Quest KACE, all versions prior to version 8.0.x, 8.1.x, and 9.0.x, allows unintentional access to the appliance leveraging functions of the…
published 7y ago modified 4mo ago also EUVD-2019-2687
- cvss
- 7.2
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Quest KACE, all versions prior to version 8.0.x, 8.1.x, and 9.0.x, allows unintentional access to the appliance leveraging functions of the troubleshooting tools located in the administrator user interface.
Patch / fix
Is CVE-2019-10973 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-19-183-02 updated cvss 2.7
Quest KACE Systems Management Appliance
-
Quest KACE SMA 8.1.x, 9.0.x, 8.0.xaffected: mitigation “Quest recommends affected users upgrade to Version 9.1 or newer, which can be downloaded from the Quest support portal at the following link:” support.quest.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
2.37% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.2 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
Affected products
- n/a Quest KACE
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
us-cert.gov
/ics/advisories/icsa-19-183-02
patch, third-party-advisory, us-government-resource
-
securityfocus.com
/bid/109001
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-10973
- NVD CVE-2019-10973
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.