dbcve.org
F5os AOperating system · F5

CVE-2024-23607

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 1.4.0 / 1.6.0 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
A directory traversal vulnerability exists in the F5OS QKView utility that allows an authenticated attacker to read files outside the QKView directory.  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 directory traversal vulnerability exists in the F5OS QKView utility that allows an authenticated attacker to manipulate file paths using traversal sequences (such as ../) to access files outside the intended QKView directory, potentially exposing sensitive system files.

MitigationImplement strict input validation and path sanitization in the QKView utility to ensure all file path inputs are normalized and constrained to the allowed directory. Verify authentication mechanisms are properly enforcing access 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
F5os AOperating system
Affected:>= 1.3.0, < 1.4.0
F5os COperating system
Affected:>= 1.3.0, < 1.6.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
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. Identify F5OS platform variant
    Determine whether your system is running F5OS-A (appliance) or F5OS-C (container) by checking the system model or platform documentation provided by F5.
    Affected if The system is running F5OS-A or F5OS-C and the version falls within affected ranges.
  2. Determine installed F5OS version
    Use the F5OS command line interface or management interface to retrieve the installed software version. Typically accessed via 'show version' or through the web UI system information page.
    Affected if The installed version is >= 1.3.0 but < 1.4.0 for F5OS-A, or >= 1.3.0 but < 1.6.0 for F5OS-C.
  3. Confirm QKView utility is accessible
    Verify that the QKView diagnostic utility is enabled and accessible on the system. This may be available via CLI command or through the management interface.
    Affected if The QKView utility is enabled and operational on the affected version.
  4. Verify authentication configuration
    Review user access controls and authentication settings for the QKView utility to determine if untrusted or low-privilege accounts can invoke the QKView function.
    Affected if Users with limited privileges can access the QKView utility without additional restrictions.

You are affected if your system runs F5OS-A version 1.3.0 to < 1.4.0 or F5OS-C version 1.3.0 to < 1.6.0, and the QKView utility 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.

dbcve · scoped
Upgrade available Upgrade to 1.4.0 / 1.6.0 or later
Fixed in 1.4.01.6.0
Interim mitigation

Implement strict input validation and path sanitization in the QKView utility to ensure all file path inputs are normalized and constrained to the allowed directory. Verify authentication mechanisms are properly enforcing access controls.

Recommended fix Moderate confidence

F5os A: >= 1.4.0 | F5os C: >= 1.6.0

  1. Verify current F5OS version by running 'show system version' or checking the management interface
  2. Download the appropriate F5OS firmware image from F5 Networks support portal (my.f5.com) for your platform
  3. Review F5 release notes for version 1.4.0 (F5os A) or version 1.6.0 (F5os C) to confirm security fix inclusion
  4. Back up current configuration using 'save sys config' or the management interface
  5. Upload the new firmware image to the F5 device
  6. Install the upgrade via 'install system image <filename>' command or through the web interface
  7. Reboot the system to complete the upgrade
  8. Verify the new version is running and validate that the QKView functionality works correctly
Caveat Upgrading F5OS may require configuration adjustments; review release notes for compatibility notes and ensure backup before proceeding

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

Fix this in F5os A Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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