CVE-2019-19151
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 versions 15.0.0-15.1.0, 14.0.0-14.1.2.3, 13.1.0-13.1.3.2, 12.1.0-12.1.5, and 11.5.2-11.6.5.1, BIG-IQ versions 7.0.0, 6.0.0-6.1.0, and 5.0.0-5.4.0, iWorkflow version 2.3.0, and Enterprise Manager version 3.1.1, authenticated users granted TMOS Shell (tmsh) privileges are able access objects on the file system which would normally be disallowed by tmsh restrictions. This allows for authenticated, low privileged attackers to access objects on the file system which would not normally be allowed.
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 confidenceAuthenticated users with TMOS Shell (tmsh) privileges can bypass tmsh restrictions to access objects on the file system that should be disallowed. This is an authorization bypass vulnerability allowing low-privileged tmsh users to read files outside their intended scope.
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>= 5.0.0, <= 5.4.0>= 6.0.0, <= 6.1.0= 7.0.0>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.1.0>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.1.0>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.1.0>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.1.0>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.1.0>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.1.0>= 11.5.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.0.0, <= 13.1.3>= 14.0.0, <= 14.1.2>= 15.0.0, <= 15.1.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 installed F5 product and versionRun `tmsh show sys version` or `bigpipe version` to determine the exact product and version installedAffected if The version falls within any of the affected ranges: Big-IQ 5.0.0-5.4.0, 6.0.0-6.1.0, 7.0.0 or Big-IP 11.5.1-11.6.5, 12.1.0-12.1.5, 13.0.0-13.1.3, 14.0.0-14.1.2, 15.0.0-15.1.0 for any module (APM, AFM, Analytics, AAM, ASM, DNS, Edge Gateway)
-
Confirm tmsh shell access is enabledCheck user role configurations via `tmsh list auth user` or review administrative user accounts in the F5 management interfaceAffected if Any user account has tmsh or administrator role privileges configured on the system
-
Review user account privilegesRun `tmsh list auth user all-properties` to enumerate all local users and their assigned rolesAffected if There are user accounts assigned to roles other than Administrator that still have tmsh shell access
-
Check for low-privileged tmsh usersIdentify users with the 'guest' or custom 'tmsh' role by reviewing output from `tmsh list auth role` and `tmsh show auth user`Affected if Non-administrative user accounts exist with tmsh shell access privileges
-
Audit file system access logsReview system logs and bash history for any anomalous file read operations from tmsh context, checking for access to paths outside /var or /configAffected if Logs show file read operations from tmsh sessions accessing paths outside the expected tmsh-restricted directories
The environment is affected if the installed F5 product version falls within the vulnerable ranges AND there are user accounts with tmsh shell privileges that could potentially bypass intended file system restrictions.
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 dataApply F5 security patches for the affected versions. Restrict tmsh privileges to only essential administrative users and review user role assignments to limit exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19151 — 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-19151 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