Big Ip Access Policy ManagerApplication · F5

CVE-2023-22340

HIGH · 7.5 CVSS v3.1 Published 2023-02-01

Fix available

A fix is available. Upgrade to 14.1.5.3 / 15.1.8 or later.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

On BIG-IP versions 16.1.x before 16.1.3.3, 15.1.x before 15.1.8, 14.1.x before 14.1.5.3, and all versions of 13.1.x, when a SIP profile is configured on a Message Routing type virtual server, undisclosed traffic can cause TMM to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Technical summary

dbcve analysis · high confidence

This is a denial of service vulnerability in F5 BIG-IP where specially crafted undisclosed traffic sent to a virtual server configured with a SIP profile and Message Routing type causes the TMM (Traffic Management Microkernel) to terminate, resulting in service disruption.

MitigationUpgrade BIG-IP to the patched versions (16.1.3.3+, 15.1.8+, 14.1.5.3+) or remove the SIP profile from affected Message Routing virtual servers if upgrading is not immediately feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Big Ip Access Policy ManagerApplication

Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2

Big Ip Advanced Firewall ManagerApplication

Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2

Big Ip AnalyticsApplication

Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2

Big Ip Application Acceleration ManagerApplication

Affected:>= 13.1.0, <= 13.1.5>= 15.1.0, < 15.1.8>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2

Big Ip Application Security ManagerApplication

Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2

Big Ip Ddos Hybrid DefenderApplication

Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8>= 16.1.0, < 16.1.3.3

Big Ip Domain Name SystemApplication

Affected:>= 14.1.0, < 14.1.5.3>= 15.1.0, < 15.1.8>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2

Big Ip Fraud Protection ServiceApplication

Affected:>= 13.1.0, <= 13.1.5>= 15.1.0, < 15.1.8>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check BIG-IP version

Run `tmsh show sys version` or `tmsh show /sys version` to obtain the installed BIG-IP version.

Affected if Version falls within 13.1.0-13.1.5, 14.1.0-14.1.5.2, 15.1.0-15.1.7, 16.1.0-16.1.3.2, or 17.0.0-17.0.0.1.
Identify SIP profiles configured

Run `tmsh list /ltm profile sip` to list all SIP profiles defined on the system.

Affected if Any SIP profiles exist in the configuration.
Identify virtual servers with SIP profile

Run `tmsh list /ltm virtual` and filter for entries that reference a SIP profile in their properties.

Affected if Any virtual server references a SIP profile in its configuration.
Check virtual server type for Message Routing

For each virtual server with a SIP profile, run `tmsh list /ltm virtual <name>` and examine the 'type' field.

Affected if The virtual server type is set to 'message-routing' or 'performance (layer 4)' with message routing enabled.

The environment is affected if the BIG-IP version is within the vulnerable ranges AND a virtual server is configured with both a SIP profile and Message Routing type.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 14.1.5.3 / 15.1.8 / 16.1.3.3 or later

Fixed in 14.1.5.315.1.816.1.3.3

Interim mitigation

Upgrade BIG-IP to the patched versions (16.1.3.3+, 15.1.8+, 14.1.5.3+) or remove the SIP profile from affected Message Routing virtual servers if upgrading is not immediately feasible.

Recommended fix High confidence

14.1.5.3 (for 14.1.x), 15.1.8 (for 15.1.x), 16.1.3.3 (for 16.1.x), or 17.0.0.2 (for 17.x)

1. Identify all BIG-IP devices running affected versions (13.1.0-13.1.5, 14.1.0-14.1.5.2, 15.1.0-15.1.7, 16.1.0-16.1.3.2) in the environment
2. Identify any virtual servers configured with a SIP profile that are of type 'Message Routing'
3. If possible, temporarily disable or remove the SIP profile from Message Routing virtual servers as a mitigation (this may impact SIP routing functionality)
4. Download the appropriate fixed version from F5 Networks: 14.1.5.3, 15.1.8, 16.1.3.3, or 17.0.0.2 depending on your current major version
5. Review F5 upgrade documentation and release notes for your specific platform
6. Schedule a maintenance window following F5 best practices for upgrades
7. Perform the upgrade to the appropriate fixed version
8. After upgrade, verify that TMM is running normally and SIP functionality is restored if it was disabled

Caveat Upgrading may cause brief service disruption; review F5 release notes for any configuration changes required between versions

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
Implementation4.0 h
Testing4.0 h
Review / QA2.0 h

14.0 hours of engineering $2,480

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,968.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

my.f5.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-22340 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2023-22340?

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.

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

At a glance

A fix existsUpgrade to 14.1.5.3 / 15.1.8 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.6%

Affects: Big Ip Access Policy Manager

Remediation

A high-priority fix

Fix this in Big Ip Access Policy Manager 14 hrs · Moderate

Typical engagement from $2,480

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2023-22340 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References