CVE-2022-31473
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 · uneditedIn BIG-IP Versions 16.1.x before 16.1.1 and 15.1.x before 15.1.4, when running in Appliance mode, an authenticated attacker may be able to bypass Appliance mode restrictions due to a directory traversal vulnerability in an undisclosed page within iApps. A successful exploit can allow the attacker to cross a security boundary. 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 confidenceA directory traversal vulnerability in an undisclosed page within iApps allows authenticated attackers to bypass Appliance mode restrictions on affected BIG-IP devices. The flaw enables crossing security boundaries through path traversal, potentially exposing sensitive system functions that should be restricted in Appliance mode.
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>= 15.1.0, < 15.1.4= 16.1.0CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Determine BIG-IP APM versionRun the command 'tmsh show /sys version' or 'b version' on the command line, or check System > Software > Image in the web management interfaceAffected if The installed version falls within >= 15.1.0 and < 15.1.4, or equals exactly 16.1.0
-
Verify Appliance mode is configuredRun 'tmsh show /sys apm-settings' or check the APM configuration via the web UI under Access Policy > APM Settings to confirm Appliance mode restrictions are in placeAffected if Appliance mode is enabled on the device (the bypass targets this specific security mode)
-
Confirm iApps is accessibleCheck if the iApps interface is accessible via the web UI (Local Traffic > iApps) or via tmsh by listing active iApps packages with 'tmsh list sys app']Affected if iApps is deployed and accessible on the BIG-IP device, making the undisclosed page potentially reachable
A system is affected if it runs BIG-IP APM version 15.1.0 through 15.1.3, 15.1.4 (if unpatched), or exactly 16.1.0, has Appliance mode restrictions in place, and has iApps accessible to authenticated users who could exploit the directory traversal.
Generated from the published advisory. Verify against your own configuration.
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 · scoped15.1.4
Upgrade BIG-IP to version 16.1.1 or 15.1.4 or later to patch the directory traversal vulnerability in iApps that allows bypassing Appliance mode restrictions.
15.1.4+ for 15.1.x branch; 16.1.1+ for 16.1.x branch
- 1. Identify the current BIG-IP APM version by checking System > Software Management > IMAGE LIST or running 'tmsh show sys version'
- 2. If running 15.1.0-15.1.3, plan upgrade to 15.1.4 or later (15.1.x LTS)
- 3. If running exactly 16.1.0, plan upgrade to 16.1.1 or later
- 4. Before upgrading, back up the BIG-IP configuration using 'tmsh save sys config'
- 5. Download the appropriate hotfix from F5 Networks support portal (support.f5.com) - requires F5 account with valid support contract
- 6. Upload the ISO/image via WebUI (System > Software Management > IMAGE LIST > Upload) or CLI
- 7. Install the image and reboot using the F5 upgrade procedure: 'tmsh install sys software hotfix <image-name>'
- 8. After reboot, verify the new version is running and Appliance mode functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31473 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-31473 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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