dbcve.org
F5os AOperating system · F5

CVE-2022-41835

HIGH · 8.8 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 1.1.0 / 1.5.0 or later.
See remediation →
90/100
Remediation priority · Urgent
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.5.0, excessive file permissions in F5OS allows an authenticated local attacker to execute limited set of commands in a container and impact the F5OS controller.

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

Excessive file permissions in F5OS allows an authenticated local attacker to execute a limited set of commands within a container, potentially escalating privileges to impact the F5OS controller. This represents a container isolation bypass via improper file permission settings.

MitigationUpgrade to F5OS-A 1.1.0 or later, or F5OS-C 1.5.0 or later to address the excessive file permissions. Additionally, restrict local authenticated access and monitor for unusual container command execution.

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.3.0, < 1.5.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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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
    Determine if the system is running F5OS-A or F5OS-C variant. This can typically be done via the system dashboard, CLI command 'show system product', or by checking the model/hardware identifier.
    Affected if System is running F5OS-A or F5OS-C variant (other variants are not affected by this CVE)
  2. Check installed F5OS version
    Run the command 'show system version' or access the F5OS management interface to retrieve the currently installed software version. Record the full version number (e.g., 1.0.x or 1.4.x).
    Affected if Version information cannot be retrieved or system is not running F5OS
  3. Compare F5OS-A version against affected range
    If running F5OS-A, compare the installed version against the affected range >= 1.0.0 and < 1.1.0. Any version from 1.0.0 up to but not including 1.1.0 is affected.
    Affected if F5OS-A version is 1.0.0 or higher but lower than 1.1.0
  4. Compare F5OS-C version against affected range
    If running F5OS-C, compare the installed version against the affected range > 1.3.0 and < 1.5.0. Versions greater than 1.3.0 up to but not including 1.5.0 are affected.
    Affected if F5OS-C version is greater than 1.3.0 but lower than 1.5.0
  5. Verify local authenticated access exists
    Confirm that local user accounts with authentication credentials exist on the system. Check via 'showaaa' or similar administrative command to list local users. The vulnerability requires an authenticated local attacker to exploit.
    Affected if Local authenticated user accounts are present on the system

A system is affected if it runs F5OS-A version 1.0.0 to < 1.1.0 or F5OS-C version > 1.3.0 to < 1.5.0, and local authenticated access is available to a potential attacker.

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.5.0 or later
Fixed in 1.1.01.5.0
Interim mitigation

Upgrade to F5OS-A 1.1.0 or later, or F5OS-C 1.5.0 or later to address the excessive file permissions. Additionally, restrict local authenticated access and monitor for unusual container command execution.

Recommended fix High confidence

F5OS-A: upgrade to 1.1.0 or later; F5OS-C: upgrade to 1.5.0 or later

  1. 1. Download the appropriate fixed version of F5OS from the F5 Networks support portal (support.f5.com): F5OS-A version 1.1.0 or later, F5OS-C version 1.5.0 or later
  2. 2. Verify the integrity of the downloaded image using checksums provided on the support portal
  3. 3. Upload the new F5OS image to the F5OS device using the management interface or CLI
  4. 4. Initiate the upgrade process according to F5 documentation - typically using 'tmsh install sys software' or the web-based management interface
  5. 5. Verify the upgrade completed successfully and the system is running the fixed version
  6. 6. Confirm the fix by checking that excessive file permissions have been corrected
Caveat Review F5 release notes for version-specific upgrade considerations and ensure compatibility with existing configurations before upgrading

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

Fix this in F5os A Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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