dbcve.org
Big Ip Next Central ManagerApplication · F5

CVE-2024-32049

HIGH · 7.4 CVSS v3.1 Published 2024-05-08
Fix available
A fix is available. Upgrade to 20.1.0 or later.
See remediation →
83/100
Remediation priority · High
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
BIG-IP Next Central Manager (CM) may allow an unauthenticated, remote attacker to obtain the BIG-IP Next LTM/WAF instance credentials.  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

BIG-IP Next Central Manager contains an unauthenticated remote information disclosure vulnerability allowing attackers to obtain credentials for BIG-IP Next LTM/WAF instances. The vulnerability is exploitable without authentication, making it particularly severe for internet-facing deployments.

MitigationApply the vendor patch or upgrade to a fixed version of BIG-IP Next Central Manager. Until patched, restrict network access to the Central Manager management interface and implement additional authentication controls.

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.0.1, < 20.1.0

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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. Identify if BIG-IP Next Central Manager is deployed
    Check your F5 product inventory or running services for 'BIG-IP Next Central Manager' or 'Next CM' - this is typically a standalone appliance or virtual edition used for centralized management of BIG-IP Next instances.
    Affected if The product is not present in your environment at all, you are not affected.
  2. Determine the installed version of BIG-IP Next Central Manager
    Access the Central Manager admin interface and navigate to System > Overview, or run the command 'tmsh show /sys version' via SSH to the Central Manager appliance. Record the exact version number displayed.
    Affected if The installed version falls within the range >= 20.0.1 and < 20.1.0, indicating the vulnerability is present.
  3. Verify network accessibility of the Central Manager management interface
    Check firewall rules, security groups, or network ACLs to determine whether the Central Manager management port (typically 443 or 8443) is accessible from untrusted networks, the internet, or non-administrative internal segments.
    Affected if The management interface is exposed to untrusted networks and the version is in the affected range, the vulnerability is exploitable without authentication.
  4. Review access logs for anomalous unauthenticated requests
    Examine Central Manager access logs (typically in /var/log/httpx or via the admin UI logs) for unexpected API calls, credential retrieval attempts, or requests to administrative endpoints that occurred without prior authentication.
    Affected if Such requests are present in logs and the version is in the affected range, compromise may have occurred.

You are affected if BIG-IP Next Central Manager is installed with a version >= 20.0.1 and < 20.1.0, especially if the management interface is network-accessible from untrusted sources.

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.1.0 or later
Fixed in 20.1.0
Interim mitigation

Apply the vendor patch or upgrade to a fixed version of BIG-IP Next Central Manager. Until patched, restrict network access to the Central Manager management interface and implement additional authentication controls.

Recommended fix High confidence

20.1.0

  1. Review the BIG-IP Next Central Manager 20.1.0 release notes for upgrade considerations and any known issues
  2. Create a backup of the current BIG-IP Next Central Manager configuration
  3. Download BIG-IP Next Central Manager version 20.1.0 from F5 Networks
  4. Schedule a maintenance window to minimize disruption
  5. Follow F5's standard upgrade procedure for BIG-IP Next Central Manager to apply version 20.1.0
  6. Verify the upgrade was successful and the version is 20.1.0
  7. Confirm the vulnerability is remediated by testing that unauthenticated access no longer exposes credentials
Caveat Review release notes for any configuration or behavioral changes between 20.0.1-20.0.x and 20.1.0 before upgrading

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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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