dbcve.org
Big Ip Local Traffic ManagerApplication · F5

CVE-2019-6640

MEDIUM · 5.3 CVSS v3.1 Published 2019-07-03
Fix available
A fix is available. Upgrade to 11.5.9 / 11.6.3 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 BIG-IP 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, 11.6.1-11.6.3.4, and 11.5.1-11.5.8, SNMP exposes sensitive configuration objects over insecure transmission channels. This issue is exposed when a passphrase is inserted into various profile types and accessed using SNMPv2.

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

On affected BIG-IP versions, SNMPv2 exposes sensitive configuration objects including passphrases inserted into various profile types over insecure transmission channels, allowing potential interception of sensitive credentials.

MitigationUpgrade BIG-IP to a patched version or disable SNMPv2 and migrate to SNMPv3 with authentication and encryption to prevent exposure of sensitive configuration data.

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.5.1, < 11.5.9>= 11.6.1, < 11.6.3>= 12.1.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 Acceleration ManagerApplication
Affected:>= 11.5.1, < 11.5.9>= 11.6.1, < 11.6.4>= 12.1.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 Advanced Firewall ManagerApplication
Affected:>= 11.5.1, < 11.5.9>= 11.6.1, < 11.6.4>= 12.1.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 AnalyticsApplication
Affected:>= 11.5.1, < 11.5.9>= 11.6.1, < 11.6.4>= 12.1.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 Access Policy ManagerApplication
Affected:>= 11.5.1, < 11.5.9>= 11.6.1, < 11.6.4>= 12.1.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
Affected:>= 11.5.1, < 11.5.9>= 11.6.1, < 11.6.3>= 12.1.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 Domain Name SystemApplication
Affected:>= 11.5.1, < 11.5.9>= 11.6.1, < 11.6.4>= 12.1.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 Edge GatewayWeb browser
Affected:>= 11.5.1, < 11.5.9>= 11.6.1, < 11.6.4>= 12.1.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

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. Determine BIG-IP version
    Run `tmsh show sys version` or check the GUI under System > Software > Version
    Affected if The installed version falls within any of these ranges: >= 11.5.1 and < 11.5.9; >= 11.6.1 and < 11.6.3/11.6.4; >= 12.1.0 and < 12.1.4.1; >= 13.0.0 and < 13.1.1.5; >= 14.0.0 and < 14.0.0.5; >= 14.1.0 and < 14.1.0.6
  2. Verify SNMP service is running
    Run `tmsh list sys snmp` or check under System > SNMP > Configuration
    Affected if SNMP is enabled and the service is running on the device
  3. Confirm SNMPv2 is in use
    Examine the SNMP configuration for v2c community strings - check `tmsh list sys snmp communities`
    Affected if SNMPv2c (v2) community strings are configured, indicating v2 is enabled
  4. Identify profiles containing sensitive data
    Review profiles such as HTTP, LDAP, or gateway that may contain passphrases using `tmsh list ltm profile` and related commands
    Affected if Profiles with embedded credentials or passphrases exist and SNMPv2 is active, allowing potential credential interception

You are affected if your BIG-IP version is within the affected ranges AND SNMPv2 is enabled, because the vulnerability allows SNMPv2 to expose sensitive configuration objects including passphrases over insecure channels.

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 11.5.9 / 11.6.3 / 11.6.4 or later
Fixed in 11.5.911.6.311.6.4
Interim mitigation

Upgrade BIG-IP to a patched version or disable SNMPv2 and migrate to SNMPv3 with authentication and encryption to prevent exposure of sensitive configuration data.

Fix this in Big Ip Local Traffic 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-6640 — 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-6640 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