dbcve.org
Big Ip Next Central ManagerApplication · F5

CVE-2024-41719

MEDIUM · 5.5 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 20.2.1 or later.
See remediation →
57/100
Remediation priority · Elevated
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
When generating QKView of BIG-IP Next instance from the BIG-IP Next Central Manager (CM), F5 iHealth credentials will be logged in the BIG-IP Central Manager logs.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

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

When generating a QKView diagnostic file from BIG-IP Next Central Manager, F5 iHealth credentials are inadvertently written to the Central Manager logs. This exposes authentication credentials in plaintext within log files, potentially allowing unauthorized access to F5 iHealth services if log files are compromised.

MitigationF5 should patch the QKView generation process to prevent credential logging. Until then, restrict access to Central Manager logs and rotate any iHealth credentials that may have been exposed.

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 Next Central ManagerApplication
Affected:>= 20.1.0, < 20.2.1

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 Big-IP Next Central Manager version
    Use the command or interface to display the installed version of Big-IP Next Central Manager (for example, via 'tmsh show /sys version' or the management UI version display)
    Affected if The installed version is >= 20.1.0 and < 20.2.1
  2. Determine if QKView generation has been performed
    Review Central Manager audit logs or check for recent QKView diagnostic file creation events, which is the trigger action for this vulnerability
    Affected if A QKView diagnostic file has been generated on the system since installation
  3. Examine Central Manager logs for plaintext iHealth credentials
    Search Central Manager log files (typically found in /var/log/ or accessed via the logging service) for patterns matching iHealth username and password strings in plaintext
    Affected if Log files contain any plaintext F5 iHealth credential strings (username/password) after QKView generation

A system is affected if it runs Big-IP Next Central Manager version 20.1.0 through 20.2.0 AND a QKView diagnostic file has been generated, resulting in plaintext iHealth credentials present in logs.

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.

dbcve · scoped
Upgrade available Upgrade to 20.2.1 or later
Fixed in 20.2.1
Interim mitigation

F5 should patch the QKView generation process to prevent credential logging. Until then, restrict access to Central Manager logs and rotate any iHealth credentials that may have been exposed.

Recommended fix High confidence

20.2.1 or later

  1. Back up the current BIG-IP Next Central Manager configuration and data
  2. Download BIG-IP Next Central Manager version 20.2.1 or later from F5's download portal (my.f5.com)
  3. Follow F5's standard upgrade procedure for BIG-IP Next Central Manager: stop services, apply the upgrade, verify the installation
  4. After upgrade, verify that F5 iHealth credentials are no longer logged when generating QKView files
  5. Confirm the new version by checking the Central Manager UI or CLI

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Big Ip Next Central Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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