dbcve.org
Big Ip Local Traffic ManagerApplication · F5

CVE-2016-7469

MEDIUM · 5.4 CVSS v3.0 Published 2017-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A stored cross-site scripting (XSS) vulnerability in the Configuration utility device name change page in BIG-IP LTM, AAM, AFM, Analytics, APM, ASM, DNS, Edge Gateway, GTM, Link Controller, PEM, PSM, WebAccelerator, WOM and WebSafe version 12.0.0 - 12.1.2, 11.4.0 - 11.6.1, and 11.2.1 allows an authenticated user to inject arbitrary web script or HTML. Exploitation requires Resource Administrator or Administrator privileges, and it could cause the Configuration utility client to become unstable.

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

A stored cross-site scripting (XSS) vulnerability exists in the F5 BIG-IP Configuration utility's device name change page across multiple modules (LTM, AAM, AFM, Analytics, APM, ASM, DNS, etc.). An authenticated user with Resource Administrator or Administrator privileges can inject arbitrary JavaScript or HTML into the device name field, which persists and executes when other users access the Configuration utility, causing client instability.

MitigationApply the appropriate F5 software update for BIG-IP versions 12.0.0-12.1.2, 11.4.0-11.6.1, and 11.2.1. Until patched, restrict administrative access to trusted personnel only and consider disabling the Configuration utility for untrusted networks.

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 Local Traffic ManagerApplication
Affected:= 11.2.1= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0
Big Ip Application Acceleration ManagerApplication
Affected:= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0= 12.1.1
Big Ip Advanced Firewall ManagerApplication
Affected:= 11.2.1= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0
Big Ip AnalyticsApplication
Affected:= 11.2.1= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0
Big Ip Access Policy ManagerApplication
Affected:= 11.2.1= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0
Big Ip Application Security ManagerApplication
Affected:= 11.2.1= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.5.4= 11.6.0= 11.6.1= 12.0.0= 12.1.0
Big Ip Domain Name SystemApplication
Affected:= 12.0.0= 12.1.0= 12.1.1= 12.1.2
Big Ip Edge GatewayWeb browser
Affected:= 11.2.1

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
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checks

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

  1. Check BIG-IP software version
    Run 'tmsh show sys version' or 'tmsh show /sys version' to display the installed BIG-IP version and build number
    Affected if The installed version matches one of the affected versions listed in the CVE (e.g., 11.2.1, 11.4.0-11.6.1, 12.0.0-12.1.0 for LTM; see full list for other modules)
  2. Verify Configuration utility (GUI) is enabled
    Check if the web-based Configuration utility is accessible by attempting to reach https://<管理IP>/tmui/ or running 'tmsh show /sys httpd' to check httpd service status
    Affected if The Configuration utility (httpd service) is running and accessible on the management interface
  3. Check current device name for suspicious content
    Log into the Configuration utility and navigate to System > Platform, or run 'tmsh list /sys global-settings' to view the current device-name value. Inspect the device name field for any injected JavaScript or HTML tags
    Affected if The device name contains unexpected script tags, javascript:, onerror handlers, or other XSS payloads
  4. Identify privileged users with write access
    Run 'tmsh list /auth user' to view user accounts and their roles. Check for users assigned Resource Administrator or Administrator roles that could inject the payload
    Affected if Any user account has Resource Administrator or Administrator role assigned, allowing them to modify the device name
  5. Audit recent device name changes
    Run 'tmsh show /sys audit' or check the audit log under /var/log/audit for entries containing 'device-name' modifications around the time of potential exploitation
    Affected if Audit logs show recent changes to the device-name field, indicating possible exploitation or testing

You are affected if your BIG-IP version matches one of the listed affected versions AND the Configuration utility is accessible with any user having Resource Administrator or Administrator privileges, regardless of whether malicious content is currently visible in the device name.

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

Apply the appropriate F5 software update for BIG-IP versions 12.0.0-12.1.2, 11.4.0-11.6.1, and 11.2.1. Until patched, restrict administrative access to trusted personnel only and consider disabling the Configuration utility for untrusted networks.

Fix this in Big Ip Local 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-2016-7469 — 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-2016-7469 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