dbcve.org
Big Ip Application Acceleration ManagerApplication · F5

CVE-2019-6655

MEDIUM · 5.3 CVSS v3.1 Published 2019-09-25
Fix available
A fix is available. Upgrade to after 13.1.0.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
On versions 13.0.0-13.1.0.1, 12.1.0-12.1.4.1, 11.6.1-11.6.4, and 11.5.1-11.5.9, BIG-IP platforms where AVR, ASM, APM, PEM, AFM, and/or AAM is provisioned may leak sensitive data.

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 · moderate confidence

F5 BIG-IP platforms with AVR, ASM, APM, PEM, AFM, and/or AAM modules provisioned across versions 13.0.0-13.1.0.1, 12.1.0-12.1.4.1, 11.6.1-11.6.4, and 11.5.1-11.5.9 contain an information disclosure vulnerability that may allow sensitive data to leak. The specific data types and attack vector are not detailed in available documentation.

MitigationUpgrade BIG-IP to versions 13.1.1 or later, 12.1.5 or later, 11.6.5 or later, and 11.5.10 or later respectively. Alternatively, if upgrading is not immediately feasible, review module provisioning and restrict access to provisioned modules as a compensating control.

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 Application Acceleration ManagerApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4.1>= 13.0.0, <= 13.1.0.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4.1>= 13.0.0, <= 13.1.0.1
Big Ip AnalyticsApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4.1>= 13.0.0, <= 13.1.0.1
Big Ip Access Policy ManagerApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4.1>= 13.0.0, <= 13.1.0.1
Big Ip Application Security ManagerApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4.1>= 13.0.0, <= 13.1.0.1
Big Ip Policy Enforcement ManagerApplication
Affected:>= 11.5.2, <= 11.5.9>= 11.6.1, <= 11.6.4>= 12.1.0, <= 12.1.4.1>= 13.0.0, <= 13.1.0.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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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

  1. Identify BIG-IP version
    Run `tmsh show /sys version` on the command line or check the web UI under Dashboard > Software Version
    Affected if Version falls within 11.5.2-11.5.9, 11.6.1-11.6.4, 12.1.0-12.1.4.1, or 13.0.0-13.1.0.1
  2. Check Analytics (AVR) provisioning
    Run `tmsh list /sys provision` or check System > Provisioning in the web UI
    Affected if Analytics module is provisioned (non-None) on an affected version
  3. Check ASM provisioning
    Run `tmsh list /sys provision` or check System > Provisioning in the web UI
    Affected if Application Security Manager module is provisioned (non-None) on an affected version
  4. Check APM provisioning
    Run `tmsh list /sys provision` or check System > Provisioning in the web UI
    Affected if Access Policy Manager module is provisioned (non-None) on an affected version
  5. Check PEM provisioning
    Run `tmsh list /sys provision` or check System > Provisioning in the web UI
    Affected if Policy Enforcement Manager module is provisioned (non-None) on an affected version
  6. Check AFM/AAM provisioning
    Run `tmsh list /sys provision` or check System > Provisioning in the web UI
    Affected if Advanced Firewall Manager or Application Acceleration Manager module is provisioned (non-None) on an affected version

Environment is affected if running an affected version AND any of AVR, ASM, APM, PEM, AFM, or AAM modules are provisioned.

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
Upgrade available Upgrade to a release after 13.1.0.1
Interim mitigation

Upgrade BIG-IP to versions 13.1.1 or later, 12.1.5 or later, 11.6.5 or later, and 11.5.10 or later respectively. Alternatively, if upgrading is not immediately feasible, review module provisioning and restrict access to provisioned modules as a compensating control.

Fix this in Big Ip Application Acceleration Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6655 — 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-2019-6655 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