CVE-2024-39778
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 · uneditedWhen a stateless virtual server is configured on BIG-IP system with a High-Speed Bridge (HSB), undisclosed requests can cause TMM to terminate. 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 · moderate confidenceThis is a denial of service vulnerability in F5 BIG-IP systems where undisclosed requests sent to a stateless virtual server configured with a High-Speed Bridge (HSB) can cause the TMM (Traffic Management Module) to terminate unexpectedly, disrupting traffic processing.
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>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0>= 15.1.0, <= 15.1.1>= 16.1.0, < 16.1.5= 17.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check BIG-IP versionRun 'tmsh show sys version' or 'bigstart status' to retrieve the installed BIG-IP version. Compare against affected ranges: 15.1.0-15.1.1, 16.1.0-16.1.4, or 17.1.0Affected if Installed version falls within the affected version ranges
-
Identify virtual servers with High-Speed BridgeUse tmsh command 'tmsh list ltm virtual' to list all virtual servers, then inspect each for HSB configuration using 'tmsh list ltm virtual <name>' to see if 'high-speed-bridge' profile is assignedAffected if Any virtual server has a High-Speed Bridge (hsb) profile configured
-
Verify if HSB virtual servers are statelessFor each virtual server with HSB configured, examine the profile settings to determine if it is operating in stateless mode (check for stateless-related profile parameters or settings)Affected if The virtual server with HSB is configured as stateless (stateless mode enabled)
Environment is affected if running a BIG-IP version within 15.1.0-15.1.1, 16.1.0-16.1.4, or 17.1.0 AND has a stateless virtual server configured with a High-Speed Bridge profile.
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 · scoped16.1.5
Apply F5's vendor patch when available. Until then, restrict network access to BIG-IP systems with stateless virtual servers configured with HSB to minimize exposure to potential exploit attempts.
BIG-IP 16.1.5 (or later supported version)
- 1. Identify the currently installed BIG-IP version using 'tmsh show sys version' or the web management console.
- 2. Confirm the affected BIG-IP module (APM, AFM, ASM, etc.) is in use with stateless virtual servers and High-Speed Bridge (HSB) configuration.
- 3. Schedule a maintenance window for the upgrade, as this requires a system reboot.
- 4. Back up the current BIG-IP configuration using 'tmsh save sys config' or the web management console.
- 5. Download the fixed BIG-IP version 16.1.5 from the F5 Downloads portal (my.f5.com).
- 6. Upload and install the ISO/image via the web management console or tmsh: 'tmsh install sys software volume <volume-name> image <image-name>'.
- 7. Reboot the system to activate the new version.
- 8. Verify the upgrade was successful and the TMM process is running normally.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39778 — 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-2024-39778 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