dbcve.org
Big Ip Application Security ManagerApplication · F5

CVE-2019-6682

HIGH · 7.5 CVSS v3.1 Published 2019-12-23
Fix available
A fix is available. Upgrade to 13.1.3.2 / 14.1.2.3 or later.
See remediation →
84/100
Remediation priority · High
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 15.0.0-15.0.1.1, 14.0.0-14.1.2.2, 13.1.0-13.1.3.1, 12.1.0-12.1.5, and 11.5.2-11.6.5.1, the BIG-IP ASM system may consume excessive resources when processing certain types of HTTP responses from the origin web server. This vulnerability is only known to affect resource-constrained systems in which the security policy is configured with response-side features, such as Data Guard or response-side learning.

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

BIG-IP ASM (Application Security Manager) consumes excessive resources when processing certain HTTP responses from origin servers. This DoS condition occurs specifically when the security policy has response-side features enabled, such as Data Guard or response-side learning, and primarily affects resource-constrained systems.

MitigationUpgrade BIG-IP to fixed versions (15.1.x, 14.1.x, 13.1.x, 12.1.x, or 11.7.x) per the F5 advisory. If immediate upgrade is not feasible, consider disabling response-side ASM features or ensuring adequate system resources.

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 Security ManagerApplication
Affected:>= 11.5.2, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.2>= 14.1.0, < 14.1.2.3>= 15.0.0, < 15.1.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Identify installed BIG-IP version
    Run 'tmsh show sys version' or check the F5 BIG-IP web UI under System > Software > Image. Alternatively, 'bigpipe version' may show version details.
    Affected if The installed version falls within any of these ranges: 11.5.2-11.6.5, 12.1.0-12.1.5, 13.1.0-13.1.3.1, 14.1.0-14.1.2.2, or 15.0.0-15.0.x.
  2. Verify ASM module is provisioned
    Run 'tmsh list sys provision asm' or check via the F5 web UI under System > Resource Provisioning to confirm ASM is provisioned.
    Affected if ASM is provisioned and active on the BIG-IP device.
  3. Check for active security policies with response-side features
    In the F5 web UI, navigate to Security > Application Security > Policies. For each policy, inspect the Data Guard settings (Security > Data Guard) and response-side learning settings. Alternatively, use 'tmsh list asm policy' to list policies and check for 'response' related configurations.
    Affected if Any ASM security policy has Data Guard enabled or response-side learning active.
  4. Review system resource utilization
    Check CPU, memory, and connection table usage via 'tmsh show sys performance' or the F5 web UI under Dashboard. High resource consumption on resource-constrained systems increases exploitability.
    Affected if The system is resource-constrained (high memory/CPU usage) and the above version and policy conditions are met.

You are affected if running a vulnerable BIG-IP version AND ASM is provisioned AND at least one security policy has response-side features (Data Guard or response-side learning) enabled.

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 13.1.3.2 / 14.1.2.3 / 15.1.0 or later
Fixed in 13.1.3.214.1.2.315.1.0
Interim mitigation

Upgrade BIG-IP to fixed versions (15.1.x, 14.1.x, 13.1.x, 12.1.x, or 11.7.x) per the F5 advisory. If immediate upgrade is not feasible, consider disabling response-side ASM features or ensuring adequate system resources.

Fix this in Big Ip Application Security Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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