Access Policy Manager ClientsApplication · F5
CVE-2022-29263
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 · uneditedOn F5 BIG-IP APM 16.1.x versions prior to 16.1.2.2, 15.1.x versions prior to 15.1.5.1, 14.1.x versions prior to 14.1.4.6, 13.1.x versions prior to 13.1.5, and all versions of 12.1.x and 11.6.x, as well as F5 BIG-IP APM Clients 7.x versions prior to 7.2.1.5, the BIG-IP Edge Client Component Installer Service does not use best practice while saving temporary 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 · high confidenceThe BIG-IP Edge Client Component Installer Service saves temporary files insecurely, allowing local attackers to potentially manipulate those files to escalate privileges or execute arbitrary code. This is a classic insecure temporary file vulnerability in a privileged Windows service component.
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
Access Policy Manager ClientsApplication
= 7.1.8= 7.1.8.5= 7.1.9= 7.1.9.7= 7.1.9.8= 7.2.1= 7.2.1.1
Big Ip Access Policy ManagerApplication
= 11.6.1= 11.6.2= 11.6.3= 11.6.4= 11.6.5= 12.1.0= 12.1.1= 12.1.2= 12.1.3= 12.1.4= 12.1.5= 12.1.6CVSS 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
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Check if F5 Access Policy Manager Client is installedOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Select-Object Name,Version' in PowerShell. Look for entries named 'F5 Networks F5 Access Policy Manager Client' or similar F5 client software.Affected if The software is listed in installed programs
-
Verify the installed client versionIn Programs and Features, note the exact version number listed for F5 Access Policy Manager Client. Alternatively, check the installation directory (typically C:\Program Files\F5 Networks\) for version info in file properties.Affected if The version matches 7.1.8, 7.1.8.5, 7.1.9, 7.1.9.7, 7.1.9.8, 7.2.1, or 7.2.1.1
-
Check for the vulnerable Windows serviceOpen Services (services.msc) or run 'Get-Service | Where-Object {$_.DisplayName -like "*F5*"}' in PowerShell. Look for a service named 'F5 Edge Client Component Installer' or similar.Affected if The F5 Edge Client Component Installer Service exists and is present on the system
-
If BIG-IP APM appliance is managed, check APM versionLog into the BIG-IP Configuration Utility or run 'tmsh show sys version' via SSH on the BIG-IP device. Navigate to Access Policy > Overview > About to view the APM version.Affected if The APM version is 11.6.1 through 11.6.5, or 12.1.0 through 12.1.6
A user is affected if the F5 Access Policy Manager Client version is one of the specifically listed vulnerable versions (7.1.x or 7.2.1.x series) or if the BIG-IP APM version falls within the 11.6.x or 12.1.x branches, and the Edge Client Component Installer Service component is present.
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 · scopedUpgrade F5 BIG-IP APM to the fixed versions (16.1.2.2+, 15.1.5.1+, 14.1.4.6+, 13.1.5+) or BIG-IP APM Clients to 7.2.1.5+. For EoTS versions (12.1.x, 11.6.x), plan migration to a supported version.
Upgrade to 16.1.2.2 (or latest 16.1.x), 15.1.5.1 (or latest 15.1.x), 14.1.4.6 (or latest 14.1.x), 13.1.5 (or latest 13.1.x), or APM Clients 7.2.1.5 (or latest 7.2.x)
- Identify the current BIG-IP APM or APM Client version using 'tmsh show sys version' or the web UI.
- Compare the current version against the fixed releases: 16.1.2.2, 15.1.5.1, 14.1.4.6, 13.1.5, or APM Clients 7.2.1.5.
- If running a version prior to these fixed releases, plan an upgrade to the appropriate fixed version for your branch.
- Backup the current BIG-IP configuration before performing the upgrade.
- Download the hotfix or updated ISO from the F5 downloads page (support.f5.com) for the target fixed version.
- Follow F5 upgrade procedures: upload the image, verify integrity, and install via GUI or tmsh (tmsh install sys software).
- Reboot the device as part of the upgrade process.
- Verify the new version is running and confirm the vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Access Policy Manager Clients
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29263 — 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-29263 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