CVE-2019-16999: CloudBoot through 2019-03-08 allows SQL Injection via a crafted Status field in JSON data to the api/osinstall

Q: How do I fix CVE-2019-16999?

cloudboot: upgrade to newer than 2019-03-08. Exact commands for each OS are on this page.

Q: Is CVE-2019-16999 being exploited?

CVE-2019-16999 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-16999 affect?

CVE-2019-16999 affects cloudboot. Severity is critical (CVSS 9.8). CloudBoot through 2019-03-08 allows SQL Injection via a crafted Status field in JSON data to the api/osinstall/v1/device/getNumByStatus URI.

Q: How urgent is CVE-2019-16999?

Priority 63/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEUPGRADE

CVE-2019-16999 is a critical-severity flaw (CVSS 9.8) affecting cloudboot. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

CloudBoot through 2019-03-08 allows SQL Injection via a crafted Status field in JSON data to the api/osinstall/v1/device/getNumByStatus URI.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-89
Published	2019-09-30
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: idcos

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-09-30 13:15 UTCPublished CVE record published
2026-06-17 02:23 UTCUpdated Record last modified

idcos cloudboot UPGRADE

Affected: <= 2019-03-08

Fixed in: newer than 2019-03-08

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy cloudboot || rpm -q cloudboot || cloudboot --version

2. UPGRADE to newer than 2019-03-08 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade cloudboot

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade cloudboot

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-16999?

cloudboot: upgrade to newer than 2019-03-08. Exact commands for each OS are on this page.

Is CVE-2019-16999 being exploited?

CVE-2019-16999 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-16999 affect?

CVE-2019-16999 affects cloudboot. Severity is critical (CVSS 9.8). CloudBoot through 2019-03-08 allows SQL Injection via a crafted Status field in JSON data to the api/osinstall/v1/device/getNumByStatus URI.

How urgent is CVE-2019-16999?

Priority 63/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs