dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-34844

HIGH · 7.5 CVSS v3.1 Published 2022-08-04
Fix available
A fix is available. Upgrade to 15.1.6.1 / 16.1.3.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 BIG-IP Versions 16.1.x before 16.1.3.1 and 15.1.x before 15.1.6.1, and all versions of BIG-IQ 8.x, when the Data Plane Development Kit (DPDK)/Elastic Network Adapter (ENA) driver is used with BIG-IP or BIG-IQ on Amazon Web Services (AWS) systems, undisclosed traffic can cause the Traffic Management Microkernel (TMM) to terminate. Successful exploitation relies on conditions outside of the attacker's control. 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 confidence

A denial of service vulnerability exists in the DPDK/Elastic Network Adapter (ENA) driver used on BIG-IP and BIG-IQ systems deployed in AWS. When specially crafted undisclosed traffic is received, it causes the Traffic Management Microkernel (TMM) to terminate, disrupting traffic processing. Exploitation is less reliable due to dependence on conditions outside attacker control.

MitigationUpgrade BIG-IP to version 16.1.3.1 or later (16.1.x) and 15.1.6.1 or later (15.1.x), and BIG-IQ to a fixed version for 8.x per F5 advisory. If DPDK/ENA is not required, consider disabling it as a workaround.

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
Big Ip Access Policy ManagerApplication
Affected:>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1
Big Ip AnalyticsApplication
Affected:>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1
Big Ip Application Security ManagerApplication
Affected:>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1
Big Ip Domain Name SystemApplication
Affected:>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1
Big Ip Fraud Protection ServiceApplication
Affected:>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1
Big Ip Global Traffic ManagerApplication
Affected:>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.3.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Check BIG-IP version
    Run 'tmsh show sys version' or view version in the GUI under System > Software > Image List
    Affected if The installed version is 15.1.0 to < 15.1.6.1 or 16.1.0 to < 16.1.3.1
  2. Verify AWS deployment
    Confirm the BIG-IP virtual edition or hardware is running on AWS infrastructure. Check cloud metadata or network interface types for ENA support.
    Affected if The system is NOT deployed in AWS (the ENA driver is AWS-specific)
  3. Confirm DPDK/ENA is enabled
    Check if the Elastic Network Adapter driver is actively used. On the BIG-IP, review the network configuration or run 'tmsh show net interface' to identify ENA interfaces. In BIG-IQ, check the system inventory for DPDK-enabled network interfaces.
    Affected if DPDK/ENA is not enabled or not in use - the vulnerability only triggers when this driver handles the specially crafted traffic

You are affected if your BIG-IP/BIG-IQ version falls within 15.1.0 to < 15.1.6.1 or 16.1.0 to < 16.1.3.1, is deployed in AWS, and has DPDK/ENA driver enabled to process network traffic.

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 15.1.6.1 / 16.1.3.1 or later
Fixed in 15.1.6.116.1.3.1
Interim mitigation

Upgrade BIG-IP to version 16.1.3.1 or later (16.1.x) and 15.1.6.1 or later (15.1.x), and BIG-IQ to a fixed version for 8.x per F5 advisory. If DPDK/ENA is not required, consider disabling it as a workaround.

Recommended fix High confidence

Upgrade to BIG-IP 15.1.6.1 (for 15.1.x branch) or 16.1.3.1 (for 16.1.x branch)

  1. 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI (System > Software Management > Image List)
  2. 2. Schedule a maintenance window as the upgrade will require a brief service interruption
  3. 3. Back up the current BIG-IP configuration using 'tmsh save sys config' or via the web UI (System > Archives > Create)
  4. 4. Download the appropriate hotfix from the F5 Downloads portal (support.f5.com): For 15.1.x branches, download version 15.1.6.1; For 16.1.x branches, download version 16.1.3.1
  5. 5. Upload the ISO image to the BIG-IP via the web UI (System > Software Management > Image List > Import) or via tmsh: 'tmsh install sys software iso <filename>'
  6. 6. Create a new boot partition (Volume) for the upgrade via the web UI (System > Software Management > Volume List > Create) or via tmsh
  7. 7. Install the downloaded software onto the new volume: 'tmsh install sys software volume <volume-name> image <filename>'
  8. 8. Reboot the system to boot from the new volume: 'tmsh reboot'
Caveat Standard BIG-IP hotfix upgrade typically does not cause configuration issues; ensure configuration backup before proceeding

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

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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