dbcve.org
Big Ip Global Traffic ManagerApplication · F5

CVE-2015-8022

HIGH · 7.5 CVSS v3.0 Published 2016-08-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
The Configuration utility in F5 BIG-IP LTM, Analytics, APM, ASM, GTM, and Link Controller 11.x before 11.2.1 HF16, 11.3.x, 11.4.x before 11.4.1 HF10, 11.5.x before 11.5.4, and 11.6.x before 11.6.1; BIG-IP AAM 11.4.x before 11.4.1 HF10, 11.5.x before 11.5.4, and 11.6.x before 11.6.1; BIG-IP AFM and PEM 11.3.x, 11.4.x before 11.4.1 HF10, 11.5.x before 11.5.4, and 11.6.x before 11.6.1; BIG-IP Edge Gateway, WebAccelerator, and WOM 11.x before 11.2.1 HF16 and 11.3.0; and BIG-IP PSM 11.x before 11.2.1 HF16, 11.3.x, and 11.4.x before 11.4.1 HF10 allows remote authenticated users with certain permissions to gain privileges by leveraging an Access Policy Manager customization configuration section that allows file uploads.

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 confidence

F5 BIG-IP Configuration utility contains a privilege escalation vulnerability where remote authenticated users with certain permissions can gain elevated privileges by exploiting the Access Policy Manager (APM) customization configuration section that allows file uploads. This affects multiple BIG-IP modules including LTM, APM, ASM, GTM, and others across versions 11.x through 11.6.x.

MitigationUpgrade to F5 BIG-IP versions 11.2.1 HF16, 11.4.1 HF10, 11.5.4, or 11.6.1 or later as appropriate for the deployed version. Alternatively, restrict Access Policy Manager configuration permissions to only trusted administrators and monitor for unauthorized configuration changes.

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
Big Ip Global Traffic ManagerApplication
Affected:= 11.0.0= 11.1.0= 11.2.0= 11.2.1= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.6.0
Big Ip Local Traffic ManagerApplication
Affected:= 11.0.0= 11.1.0= 11.2.0= 11.2.1= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.6.0
Big Ip WebacceleratorApplication
Affected:= 11.0.0= 11.1.0= 11.2.0= 11.2.1= 11.3.0
Big Ip Policy Enforcement ManagerApplication
Affected:= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.6.0
Big Ip Advanced Firewall ManagerApplication
Affected:= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.6.0
Big Ip Access Policy ManagerApplication
Affected:= 11.0.0= 11.1.0= 11.2.0= 11.2.1= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.6.0
Big Ip AnalyticsApplication
Affected:= 11.0.0= 11.1.0= 11.2.0= 11.2.1= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.6.0
Big Ip Wan Optimization ManagerApplication
Affected:= 11.0.0= 11.1.0= 11.2.0= 11.2.1= 11.3.0

CVSS 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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check BIG-IP version
    Run 'tmsh show sys version' or view version in the web UI under System > Software Information
    Affected if Version matches 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, or 11.6.0
  2. Verify APM module is provisioned
    Run 'tmsh list sys provision apm' or check via the web UI under System > Provisioning
    Affected if APM provisioning level is set to Nominal or Dedicated (not None)
  3. Confirm APM access policy with customization exists
    Navigate to Access Policy > APM > Customization in the web UI or inspect the APM configuration via 'tmsh list apm profile access'
    Affected if An APM access profile with customization settings is configured and active
  4. Check for file upload capability in APM customization
    Examine APM customization configuration for file upload or resource assignment settings under Access Policy > Customization > General
    Affected if APM customization includes file upload or resource assignment features enabled for user-accessible policies
  5. Review user permissions to APM configuration
    Inspect user roles and permissions via 'tmsh list auth user' or the web UI under User Management > User Roles
    Affected if Any user role includes Access Policy Manager configuration write permissions beyond the administrator account

You are affected if your BIG-IP version is one of the listed affected versions AND the APM module is provisioned with an access policy that includes customization/file upload capabilities accessible to non-administrator users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to F5 BIG-IP versions 11.2.1 HF16, 11.4.1 HF10, 11.5.4, or 11.6.1 or later as appropriate for the deployed version. Alternatively, restrict Access Policy Manager configuration permissions to only trusted administrators and monitor for unauthorized configuration changes.

Fix this in Big Ip Global Traffic Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-8022 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-8022 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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