dbcve.org
Big Ip Next Central ManagerApplication · F5

CVE-2024-21793

HIGH · 7.5 CVSS v3.1 Published 2024-05-08
Fix available
A fix is available. Upgrade to 20.2.0 or later.
See remediation →
84/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
An OData injection vulnerability exists in the BIG-IP Next Central Manager API (URI).  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 · moderate confidence

OData injection vulnerability in F5 BIG-IP Next Central Manager API allows attackers to manipulate OData query parameters to inject malicious payloads, potentially extracting or modifying data. The vulnerability is network-exploitable via the API URI.

MitigationApply F5 security updates when available; implement strict input validation on OData query parameters; consider restricting API access or deploying WAF rules to filter malicious OData syntax.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the installed BIG-IP Next Central Manager version
    Use the F5 management interface, CLI (tmsh or similar), or API to retrieve the Central Manager version. Typically accessible via the web UI under System > Software Management or via API endpoint /mgmt/shared/system version.
    Affected if The installed version is 20.0.1 or higher but lower than 20.2.0, placing it within the affected range.
  2. Confirm Central Manager API is network accessible
    Verify if the Central Manager API port/endpoint is exposed to network attackers. Check firewall rules, reverse proxy configurations, and access profiles governing API access. The API typically listens on port 443 or a configured management IP.
    Affected if The API is reachable from untrusted networks without strong access controls, enabling external attackers to send malicious OData queries.
  3. Locate OData-enabled API endpoints
    Review available API endpoints in the Central Manager documentation or enumerate /mgmt/* paths. OData queries typically appear in URIs containing $filter, $select, $orderby, or similar OData syntax parameters.
    Affected if The Central Manager exposes OData queryable endpoints that accept user-supplied parameters in the URI query string.
  4. Inspect API request logging and traffic
    Examine API access logs, audit logs, or traffic captures for OData-related query patterns. Look for requests containing OData operators like eq, ne, gt, lt, and, or, or contains in query parameters.
    Affected if OData query parameters are being processed without visible input sanitization or validation in the request handling.

You are affected if BIG-IP Next Central Manager version falls between 20.0.1 and 20.2.0 (inclusive of 20.0.1, exclusive of 20.2.0) AND the API is accessible to potential attackers who could inject malicious OData syntax into query parameters.

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.0 or later
Fixed in 20.2.0
Interim mitigation

Apply F5 security updates when available; implement strict input validation on OData query parameters; consider restricting API access or deploying WAF rules to filter malicious OData syntax.

Recommended fix High confidence

20.2.0 or later

  1. Upgrade BIG-IP Next Central Manager to version 20.2.0 or later

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,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 $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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