CVE-2018-15333
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 versions 11.2.1. and greater, unrestricted Snapshot File Access allows BIG-IP system's user with any role, including Guest Role, to have access and download previously generated and available snapshot files on the BIG-IP configuration utility such as QKView and TCPDumps.
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 confidenceF5 BIG-IP systems version 11.2.1 and later contain an authorization bypass where users assigned ANY role, including the lowest Guest role, can access and download previously generated snapshot files (QKView outputs and TCPDumps) through the configuration utility. The system fails to enforce role-based access controls on these sensitive diagnostic files.
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.2.1, <= 11.6.3>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1>= 14.0.0, <= 14.1.0>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1>= 14.0.0, <= 14.1.0>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1>= 14.0.0, <= 14.1.0>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1>= 14.0.0, <= 14.1.0>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1>= 14.0.0, <= 14.1.0>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1>= 14.0.0, <= 14.1.0>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1>= 14.0.0, <= 14.1.0>= 11.2.1, <= 11.6.3>= 12.1.0, <= 12.1.4>= 13.0.0, <= 13.1.1>= 14.0.0, <= 14.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.0/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.
-
Check F5 BIG-IP versionRun 'tmsh show sys version' or access System > Software Management > ISO Image in the configuration utility to determine the installed versionAffected if The installed version falls within 11.2.1-11.6.3, 12.1.0-12.1.4, 13.0.0-13.1.1, or 14.0.0-14.1.0
-
Identify existing QKView snapshot filesRun 'ls -la /var/log/qkview/' or check the configuration utility at System > Logs > Auto Diagnostic Outputs for generated QKView filesAffected if Any QKView or TCPDump snapshot files exist on the system
-
Verify user role configurationRun 'tmsh list auth user' to list all users and their assigned roles, or view in the configuration utility under User Management > User ListAffected if Any user account exists with Guest, Operator, or any non-administrative role and has access to the configuration utility
-
Test diagnostic file access with limited roleLog into the configuration utility using a Guest-level or other limited role account and attempt to navigate to System > Logs > Auto Diagnostic Outputs or directly access diagnostic file URLsAffected if A user with Guest or minimal role can view or download snapshot files without permission error
You are affected if your F5 BIG-IP version is within the vulnerable ranges AND any diagnostic snapshot files exist AND users with limited roles can access the configuration utility.
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 dataRestrict access to snapshot files based on user role permissions. Apply available F5 hotfixes or upgrade to a patched version. If no patch exists, implement network-level controls to limit which users can access the configuration utility and consider disabling anonymous/guest access to sensitive endpoints.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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 $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15333 — 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-2018-15333 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