dbcve.org
Big Ip Next Cloud Native Network FunctionsApplication · F5

CVE-2024-23306

HIGH · 7.1 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 1.2.0 or later.
See remediation →
73/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
A vulnerability exists in BIG-IP Next CNF and SPK systems that may allow access to undisclosed sensitive files.  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

A file disclosure vulnerability in F5 BIG-IP Next CNF and SPK allows unauthorized access to undisclosed sensitive files, likely through a path traversal or improper access control mechanism in the web interface or API.

MitigationApply available patches from F5 for BIG-IP Next CNF and SPK; restrict network access to management interfaces; audit exposed sensitive files.

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 Cloud Native Network FunctionsApplication
Affected:>= 1.1.0, < 1.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 the installed version of F5 BIG-IP Next CNF
    Run 'tmsh show /version' or check the F5 Next CNF appliance management console for the current software version
    Affected if The installed version is 1.1.0 or higher but lower than 1.2.0
  2. Confirm the F5 Next CNF management interface is accessible
    Verify if the web-based management interface or API endpoint is exposed by checking network listeners (e.g., 'netstat -an | grep 443' or reviewing firewall rules)
    Affected if The management interface or API is network-accessible from untrusted networks
  3. Check for anomalous file access logs
    Review access logs for the management interface (typically in /var/log/httpx/ or via the logging subsystem) for suspicious requests involving path traversal patterns such as '../', '..\', or absolute paths to sensitive system files
    Affected if Logs contain requests with traversal patterns or access to system files outside the intended web root
  4. Verify access control configuration
    Examine the F5 Next CNF access policy and API authentication settings through the management interface or by reviewing configuration files in /config/
    Affected if Access controls are misconfigured, allow unauthenticated access, or do not properly restrict file system paths
  5. Inspect for unauthorized sensitive file exposure
    Compare the list of files accessible via the web interface/API against the expected file set; check if files like /etc/passwd, /etc/shadow, configuration databases, or certificates are retrievable without proper authentication
    Affected if Sensitive files not intended for web access can be retrieved through the management interface or API

You are affected if F5 BIG-IP Next CNF version 1.1.0 through 1.1.x is running and the management interface or API is accessible, with evidence of path traversal or unauthorized file access in logs or configuration.

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 1.2.0 or later
Fixed in 1.2.0
Interim mitigation

Apply available patches from F5 for BIG-IP Next CNF and SPK; restrict network access to management interfaces; audit exposed sensitive files.

Recommended fix Moderate confidence

BIG-IP Next CNF version 1.2.0 or later

  1. 1. Review the current BIG-IP Next CNF installation to confirm the installed version is within the affected range (>= 1.1.0, < 1.2.0)
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Back up current configuration data according to F5 best practices
  4. 4. Upgrade BIG-IP Next CNF to version 1.2.0 or later
  5. 5. Verify the upgrade was successful and the system is operational
  6. 6. Confirm the vulnerability is remediated by reviewing system logs and performing security validation

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

Fix this in Big Ip Next Cloud Native Network Functions 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-2024-23306 — 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-23306 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