dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2019-6613

MEDIUM · 5.3 CVSS v3.1 Published 2019-05-03
Fix available
A fix is available. Upgrade to 11.5.9 / 11.6.4 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 13.0.0-13.1.1.4, 12.1.0-12.1.4, 11.6.1-11.6.3.4, and 11.5.2-11.5.8, SNMP may expose sensitive configuration objects over insecure transmission channels. This issue is exposed when a passphrase is used with various profile types and is 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 F5 BIG-IP devices running affected versions (11.5.2-11.5.8, 11.6.1-11.6.3.4, 12.1.0-12.1.4, 13.0.0-13.1.1.4), SNMPv2 can expose sensitive configuration objects including passphrases used in various profile types over unencrypted/insecure transmission channels, allowing potential interception or unauthorized access to credential material.

MitigationMigrate from SNMPv2 to SNMPv3 which provides authentication and encryption, or restrict SNMP access to trusted networks and disable SNMP if not required. F5 has published advisories with specific version patches that should be applied.

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:>= 11.5.2, < 11.5.9>= 11.6.1, < 11.6.4>= 12.1.0, < 12.1.4.1>= 13.0.0, < 13.1.1.5
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.1.5
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.1.5
Big Ip Link ControllerApplication
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.1.5
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.1.5
Big Ip WebacceleratorApplication
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.1.5
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.1.5
Big Ip Local Traffic 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.1.5

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. Check the BIG-IP version
    Run `tmsh show /sys version` or check the web UI under System > Software > Version
    Affected if Version falls within 11.5.2-11.5.8, 11.6.1-11.6.3.4, 12.1.0-12.1.4, or 13.0.0-13.1.1.4 (or is below the fixed versions)
  2. Verify SNMP is enabled
    Run `tmsh show /snmp` or check the web UI under Network > SNMP
    Affected if SNMP daemon is running and enabled on the device
  3. Confirm SNMP version in use
    Run `tmsh list /snmp` to view the SNMP configuration, or check the SNMP agent settings in the web UI
    Affected if SNMPv2 or SNMPv2c is configured (v3 provides encryption; v2/v2c do not)
  4. Check SNMP community string exposure
    Review SNMP access controls: run `tmsh list /snmp community` and verify the community string is not transmitted over untrusted networks
    Affected if SNMPv2 with community strings accessible from untrusted networks (no ACL restriction or VLAN isolation)

The environment is affected if the BIG-IP version is within the vulnerable ranges AND SNMPv2 is enabled with accessible community strings over unencrypted 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.4 / 12.1.4.1 or later
Fixed in 11.5.911.6.412.1.4.1
Interim mitigation

Migrate from SNMPv2 to SNMPv3 which provides authentication and encryption, or restrict SNMP access to trusted networks and disable SNMP if not required. F5 has published advisories with specific version patches that should be applied.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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