dbcve.org
F5os AOperating system · F5

CVE-2022-41780

MEDIUM · 5.5 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 1.1.0 / 1.4.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
In F5OS-A version 1.x before 1.1.0 and F5OS-C version 1.x before 1.4.0, a directory traversal vulnerability exists in an undisclosed location of the F5OS CLI that allows an attacker to read arbitrary files.

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 in the F5OS CLI (undisclosed location) allows authenticated attackers to read arbitrary files on the filesystem by manipulating path traversal sequences (e.g., ../../../'). The vulnerability affects F5OS-A before 1.1.0 and F5OS-C before 1.4.0.

MitigationUpgrade F5OS-A to version 1.1.0 or later, and F5OS-C to version 1.4.0 or later to patch the directory traversal vulnerability. If immediate patching is not feasible, restrict CLI access to trusted personnel and monitor for anomalous file access patterns.

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.0.0, < 1.1.0
F5os COperating system
Affected:> 1.1.0, < 1.4.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 product variant
    Access the F5OS CLI and run 'show system version' or check the system product identifier to determine if the device is running F5OS-A or F5OS-C variant
    Affected if The product variant is F5OS-A or F5OS-C and the version falls within the affected ranges below
  2. Determine installed F5OS version
    Run 'show system version' or 'show version' command in the F5OS CLI to retrieve the exact version number
    Affected if Version is less than 1.1.0 for F5OS-A, or version is 1.1.0 through 1.4.0 (exclusive) for F5OS-C
  3. Verify CLI access is enabled
    Check if the F5OS CLI service is accessible by attempting to log in via SSH or console, or review the CLI service configuration via 'show running-config' under the CLI management settings
    Affected if CLI access is enabled and the version is vulnerable as determined above
  4. Confirm path traversal exposure
    As an authenticated CLI user, attempt to access a file outside the intended directory using path traversal syntax (e.g., 'cat ../../../etc/passwd') to verify the vulnerability exists
    Affected if The command successfully reads files outside the expected directory scope, confirming the directory traversal flaw is present

A user is affected if they are running F5OS-A before version 1.1.0 or F5OS-C between versions 1.1.0 and 1.4.0, with the CLI interface 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.1.0 / 1.4.0 or later
Fixed in 1.1.01.4.0
Interim mitigation

Upgrade F5OS-A to version 1.1.0 or later, and F5OS-C to version 1.4.0 or later to patch the directory traversal vulnerability. If immediate patching is not feasible, restrict CLI access to trusted personnel and monitor for anomalous file access patterns.

Recommended fix Moderate confidence

F5OS-A: upgrade to 1.1.0 or later | F5OS-C: upgrade to 1.4.0 or later

  1. Verify current F5OS version using 'show system version' or 'tmsh show /sys version' in CLI
  2. For F5OS-A: Upgrade to version 1.1.0 or later to remediate the path traversal vulnerability
  3. For F5OS-C: Upgrade to version 1.4.0 or later to remediate the path traversal vulnerability
  4. After upgrade, verify the system is operational and the F5OS CLI functions normally
  5. Review F5OS CLI access controls and consider network segmentation to limit exposure to CLI interfaces
Caveat Review F5OS release notes for any configuration or behavioral changes between current and target versions before upgrading

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

Fix this in F5os A Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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