CVE-2022-28716
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 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 11.6.x, a DOM-based cross-site scripting (XSS) vulnerability exists in an undisclosed page of the BIG-IP AFM, CGNAT, and PEM Configuration utility that allows an attacker to execute JavaScript in the context of the currently logged-in user. 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 confidenceA DOM-based cross-site scripting (XSS) vulnerability in F5 BIG-IP AFM, CGNAT, and PEM Configuration utility allows attackers to execute malicious JavaScript in the context of currently logged-in users through an undisclosed page. The vulnerability stems from improper handling of user-supplied input in the DOM.
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>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.5>= 14.1.0, < 14.1.4.6>= 15.1.0, < 15.1.5.1>= 16.1.0, < 16.1.2.2>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.5>= 14.1.0, < 14.1.4.6>= 15.1.0, < 15.1.5.1>= 16.1.0, < 16.1.2.2>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, < 13.1.5>= 14.1.0, < 14.1.4.6>= 15.1.0, < 15.1.5.1>= 16.1.0, < 16.1.2.2CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify installed BIG-IP versionLog into the BIG-IP Configuration utility and navigate to System > Software Management > ISO Image, or run 'tmsh show sys version' via command line to retrieve the exact software version.Affected if The installed version falls within any of these ranges: 11.6.1-11.6.5, 12.1.0-12.1.6, 13.1.0-13.1.4, 14.1.0-14.1.4.5, 15.1.0-15.1.5.0, or 16.1.0-16.1.2.1.
-
Check if AFM module is provisionedRun 'tmsh list sys provision module' or navigate to System > Software Management > Provisioning in the web interface to see which modules are provisioned.Affected if The Advanced Firewall Manager (AFM) module is provisioned on the system.
-
Check if CGNAT module is provisionedRun 'tmsh list sys provision module' or check System > Software Management > Provisioning to see if Carrier Grade NAT is provisioned.Affected if The Carrier Grade NAT (CGNAT) module is provisioned on the system.
-
Check if PEM module is provisionedRun 'tmsh list sys provision module' or check System > Software Management > Provisioning to see if Policy Enforcement Manager is provisioned.Affected if The Policy Enforcement Manager (PEM) module is provisioned on the system.
-
Confirm Configuration utility accessVerify that the BIG-IP Configuration utility (web-based management interface) is accessible. This is typically on port 443 or 8443.Affected if The Configuration utility is accessible and the affected modules (AFM, CGNAT, or PEM) are provisioned on a vulnerable version.
A system is affected if it runs a vulnerable BIG-IP version (11.6.1-11.6.5, 12.1.0-12.1.6, 13.1.0-13.1.4, 14.1.0-14.1.4.5, 15.1.0-15.1.5.0, or 16.1.0-16.1.2.1) AND has AFM, CGNAT, or PEM modules provisioned, with the Configuration utility accessible.
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 · scoped13.1.514.1.4.615.1.5.1
Apply the vendor-supplied patches (16.1.2.2+, 15.1.5.1+, 14.1.4.6+, 13.1.5+) to the BIG-IP system. For end-of-life versions (12.1.x, 11.6.x), restrict administrative access to trusted networks or implement additional web application firewall protections.
Upgrade to the earliest fixed version in your current major branch: 14.1.4.6 for 14.1.x, 13.1.5 for 13.1.x, 15.1.5.1 for 15.1.x, or 16.1.2.2 for 16.1.x. Versions 11.6.x and 12.1.x have no fix available as they are End of Technical Support.
- 1. Identify the current BIG-IP version by navigating to System > Software Management > ISO Image or checking the version displayed on the login page
- 2. Determine which major version line (11.6.x, 12.1.x, 13.1.x, 14.1.x, 15.1.x, or 16.1.x) is currently installed
- 3. For 14.1.x versions: upgrade to version 14.1.4.6 or later
- 4. For 13.1.x versions: upgrade to version 13.1.5 or later
- 5. For 15.1.x versions: upgrade to version 15.1.5.1 or later
- 6. For 16.1.x versions: upgrade to version 16.1.2.2 or later
- 7. Note: 11.6.x and 12.1.x have no fix available; these versions have reached End of Technical Support (EoTS) and require migration to a supported version
- 8. After upgrade, verify the fix by logging into the Configuration utility and confirming the undisclosed page no longer executes arbitrary JavaScript
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28716 — 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-28716 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