CloudBoot through 2019-03-08 allows SQL Injection via a crafted Status field in JSON data to the api/osinstall/v1/device/getNumByStatus URI.
CVE-2019-16999
CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 9.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EPSS
- 70.8%
- KEV
- Not listed
Published
September 30, 2019
Last Modified
November 21, 2024
Advisory Details (1)
Auto-updated Jun 13, 2026No patch confirmed yet.
generic
Cloudboot has SQL injection · Issue #22 · idcos/Cloudboot · GitHub
https://github.com/idcos/Cloudboot/issues/22Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Frequently asked(5)
What is CVE-2019-16999?
CVE-2019-16999 is a critical vulnerability published on September 30, 2019. CloudBoot through 2019-03-08 allows SQL Injection via a crafted Status field in JSON data to the api/osinstall/v1/device/getNumByStatus URI.
When was CVE-2019-16999 disclosed?
CVE-2019-16999 was first published in the National Vulnerability Database on September 30, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-16999 actively exploited?
CVE-2019-16999 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 70.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-16999?
CVE-2019-16999 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-16999?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-16999, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2019-16999
Is Your Infrastructure Affected by CVE-2019-16999?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.