dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2019-6641

MEDIUM · 6.5 CVSS v3.1 Published 2019-07-03
Fix available
A fix is available. Upgrade to after 12.1.4 or later.
See remediation →
71/100
Remediation priority · Elevated
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
On BIG-IP 12.1.0-12.1.4.1, undisclosed requests can cause iControl REST processes to crash. The attack can only come from an authenticated user; all roles are capable of performing the attack. Unauthenticated users cannot perform this attack.

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

In BIG-IP 12.1.0-12.1.4.1, authenticated users can send undisclosed requests to the iControl REST API that cause the iControl REST processes to crash, resulting in denial of service. Any authenticated user role can trigger this vulnerability.

MitigationApply the vendor-supplied patch or upgrade to a non-vulnerable BIG-IP version. As a defense-in-depth measure, restrict iControl REST access to trusted users and 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 Access Policy ManagerApplication
Affected:>= 12.1.2, <= 12.1.4
Big Ip Advanced Firewall ManagerApplication
Affected:>= 12.1.2, <= 12.1.4
Big Ip AnalyticsApplication
Affected:>= 12.1.2, <= 12.1.4
Big Ip Application Acceleration ManagerApplication
Affected:>= 12.1.2, <= 12.1.4
Big Ip Application Security ManagerApplication
Affected:>= 12.1.2, <= 12.1.4
Big Ip Domain Name SystemApplication
Affected:>= 12.1.2, <= 12.1.4
Big Ip Edge GatewayWeb browser
Affected:>= 12.1.2, <= 12.1.4
Big Ip Fraud Protection ServiceApplication
Affected:>= 12.1.2, <= 12.1.4

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 the installed BIG-IP version
    Run the command 'tmsh show sys version' or check the web UI under System > Software > Image. Alternatively, run 'bigpipe version' to display the version.
    Affected if The installed version is between 12.1.2 and 12.1.4 (or 12.1.0-12.1.4.1 per the summary).
  2. Confirm iControl REST service is accessible
    Attempt to reach the iControl REST API endpoint (typically port 443 or 8443 with /mgmt/shared/authn/login). Check if the service responds to authenticated REST API requests using curl or a similar tool.
    Affected if iControl REST is enabled and accessible on the device.
  3. Verify the user authentication role for iControl REST
    Review user accounts in Access Policy Manager (APM) or via 'tmsh list auth user' to confirm the presence of user accounts with any role that can access iControl REST.
    Affected if Any authenticated user account exists with a role that provides iControl REST access.

A user is affected if their BIG-IP version falls within 12.1.2-12.1.4 and the iControl REST interface is accessible to authenticated 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
Upgrade available Upgrade to a release after 12.1.4
Interim mitigation

Apply the vendor-supplied patch or upgrade to a non-vulnerable BIG-IP version. As a defense-in-depth measure, restrict iControl REST access to trusted users and networks.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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