CVE-2019-6622
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 · uneditedOn BIG-IP 14.1.0-14.1.0.5, 14.0.0-14.0.0.5, 13.0.0-13.1.1.4, 12.1.0-12.1.4.1, and 11.5.1-11.6.4, an undisclosed iControl REST worker is vulnerable to command injection by an administrator or resource administrator user. This attack is only exploitable on multi-bladed systems.
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 confidenceAn authenticated command injection vulnerability exists in the iControl REST API on F5 BIG-IP devices. An administrator or resource administrator user can inject commands through an undisclosed REST worker, leading to arbitrary command execution on the underlying system. The vulnerability is specific to multi-bladed BIG-IP systems.
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>= 11.5.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.1.0.5>= 11.5.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.1.0.5>= 11.5.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.1.0.5>= 11.5.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.1.0.5>= 11.5.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.1.0.5>= 11.5.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.1.0.5>= 11.5.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.1.0.5>= 11.5.1, <= 11.6.4>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1.4>= 14.0.0, <= 14.1.0.5CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 the BIG-IP system is multi-bladedRun 'tmsh show sys hardware' or check the output of 'tmsh show sys cluster' to see if multiple blades are present. On single-blade systems or VIPRION chassis, check the 'Chassis Information' section in the web UI under Dashboard or use 'tmsh show sys hardware' and look for multiple blade entries.Affected if The system is single-bladed (not affected) - the vulnerability only affects multi-bladed BIG-IP systems
-
Determine the installed BIG-IP versionRun 'tmsh show sys version' or access the web UI and check the version displayed on the login page or under System > Software Management > ISO Image. Compare the version number against the affected ranges: 11.5.1-11.6.4, 12.1.0-12.1.4, 13.0.0-13.1.1.4, or 14.0.0-14.1.0.5.Affected if The installed version falls within any of the affected version ranges listed
-
Confirm iControl REST API is exposedVerify the iControl REST API service is running by checking the output of 'tmsh show restjavad' or by attempting a local HTTPS request to https://localhost/mgmt/shared/authz/login. Also verify port 443 (or custom management port) is open for REST access.Affected if The iControl REST API is accessible and running on the system
-
Verify administrative user access existsCheck for existing administrator or resource administrator user accounts using 'tmsh list auth user' or by reviewing user partitions and roles in the web UI under User Management > User List.Affected if Any administrator or resource administrator accounts exist on the system (authenticated access is required for exploitation)
You are affected if you have a multi-bladed BIG-IP system running a version within 11.5.1-11.6.4, 12.1.0-12.1.4, 13.0.0-13.1.1.4, or 14.0.0-14.1.0.5, with iControl REST API exposed and any administrator accounts present.
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.
From vendor dataUpgrade BIG-IP to a version beyond 14.1.0.5/14.0.0.5/13.1.1.4/12.1.4.1/11.6.4 as specified in F5 advisory K21905555. Limit administrative access to trusted personnel and audit admin account usage as an interim control.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6622 — 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-2019-6622 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