Big Ip Advanced Firewall ManagerApplication · F5
CVE-2019-6636
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 (AFM, ASM) 14.1.0-14.1.0.5, 14.0.0-14.0.0.4, 13.0.0-13.1.1.4, 12.1.0-12.1.4, and 11.5.1-11.6.4, a stored cross-site scripting vulnerability in AFM feed list. In the worst case, an attacker can store a CSRF which results in code execution as the admin user. The level of user role which can perform this attack are resource administrator and administrator.
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 confidenceStored XSS vulnerability in the AFM (Advanced Firewall Manager) feed list component of F5 BIG-IP. An authenticated attacker with resource administrator or administrator role can inject malicious JavaScript into the feed list, which persists and executes in admin browsers. This can be chained with CSRF to achieve code execution as the admin user.
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 Advanced Firewall ManagerApplication
>= 12.0.0, < 12.1.4.1>= 13.0.0, < 13.1.1.5>= 14.0.0, < 14.0.0.5>= 14.1.0, < 14.1.0.6
Big Ip Application Security ManagerApplication
>= 12.0.0, < 12.1.4.1>= 13.0.0, < 13.1.1.5>= 14.0.0, < 14.0.0.5>= 14.1.0, < 14.1.0.6CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/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 the installed BIG-IP versionRun the command to display the BIG-IP system version, such as 'tmsh show /sys version' or access the web UI to view the system information pageAffected if The installed version falls within these ranges: 12.0.0 to 12.1.4.1, 13.0.0 to 13.1.1.5, 14.0.0 to 14.0.0.5, or 14.1.0 to 14.1.0.6
-
Confirm AFM module provisioningCheck the provisioning status of the Advanced Firewall Manager module using the appropriate system command or web UI section for module provisioningAffected if AFM is provisioned and the BIG-IP version is in one of the affected ranges listed above
-
Confirm ASM module provisioningCheck the provisioning status of the Application Security Manager module using the appropriate system command or web UI section for module provisioningAffected if ASM is provisioned and the BIG-IP version is in one of the affected ranges listed above
-
Inspect AFM feed list for suspicious entriesAccess the AFM feed list component via the web UI (Security > Network Firewall > Feed List) or API and review all entries for unexpected or malicious-looking JavaScript code or encoded contentAffected if The feed list contains entries with injected JavaScript or script tags that were not intentionally added by legitimate administrators
You are affected if your BIG-IP version is within the affected ranges AND either the AFM or ASM module is provisioned, and an attacker with admin role has injected malicious script into the feed list.
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 data12.1.4.113.1.1.514.0.0.5
Upgrade BIG-IP to version 14.1.1, 14.0.1, 13.1.2, 12.1.5, or 11.6.5 or later, or apply the appropriate hotfix. Limit admin access to trusted personnel and audit feed list entries for malicious content until patching is complete.
Fix this in Big Ip Advanced Firewall Manager
Scoped from the published advisory
- 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-6636 — 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-6636 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