dbcve.org
Big Ip Local Traffic ManagerApplication · F5

CVE-2019-6634

MEDIUM · 6.5 CVSS v3.0 Published 2019-07-03
Fix available
A fix is available. Upgrade to 12.1.4.1 / 13.1.1.5 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 14.1.0-14.1.0.5, 14.0.0-14.0.0.4, 13.0.0-13.1.1.4, and 12.1.0-12.1.4, a high volume of malformed analytics report requests leads to instability in restjavad process. This causes issues with both iControl REST and some portions of TMUI. The attack requires an authenticated user with any role.

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

An authenticated user with any role can send malformed analytics report requests to BIG-IP, which destabilizes the restjavad process. This causes denial of service affecting both iControl REST API and TMUI web interface, making administrative functions unavailable.

MitigationUpgrade to a patched BIG-IP version beyond 14.1.0.5, 14.0.0.4, 13.1.1.4, or 12.1.4. If immediate upgrade is not feasible, consider restricting access to analytics report endpoints or implementing rate limiting on authenticated sessions.

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:>= 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:>= 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:>= 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:>= 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:>= 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:>= 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:>= 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:>= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/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. Check BIG-IP version
    Run `tmsh show /sys version` or access TMUI System > Software > Image List to see installed version
    Affected if Version falls within >= 12.1.0, < 12.1.4.1 OR >= 13.0.0, < 13.1.1.5 OR >= 14.0.0, < 14.0.0.5 OR >= 14.1.0, < 14.1.0.6
  2. Identify active modules
    Run `tmsh show /sys module` or check TMUI for licensed modules such as LTM, AAM, AFM, Analytics, APM, ASM, DNS, or Edge Gateway
    Affected if Any of these modules are licensed and running on a vulnerable version
  3. Verify analytics endpoint exposure
    Check if analytics reporting feature is accessible via iControl REST at /mgmt/shared/analytics/reports or through TMUI under Local Traffic > Analytics
    Affected if Analytics functionality is exposed and accessible to authenticated users
  4. Confirm restjavad service stability
    Run `tmsh show /sys service restjavad` or check if iControl REST API and TMUI are responsive
    Affected if restjavad process is unstable, unresponsive, or frequently restarting

User is affected if BIG-IP version is within any of the vulnerable ranges AND analytics module 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 12.1.4.1 / 13.1.1.5 / 14.0.0.5 or later
Fixed in 12.1.4.113.1.1.514.0.0.5
Interim mitigation

Upgrade to a patched BIG-IP version beyond 14.1.0.5, 14.0.0.4, 13.1.1.4, or 12.1.4. If immediate upgrade is not feasible, consider restricting access to analytics report endpoints or implementing rate limiting on authenticated sessions.

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-6634 — 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-6634 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