CVE-2015-6546
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 · uneditedThe vCMP host in F5 BIG-IP Analytics, APM, ASM, GTM, Link Controller, and LTM 11.0.0 before 11.6.0, BIG-IP AAM 11.4.0 before 11.6.0, BIG-IP AFM and PEM 11.3.0 before 11.6.0, BIG-IP Edge Gateway, WebAccelerator, and WOM 11.0.0 through 11.3.0, BIG-IP PSM 11.0.0 through 11.4.1 allows remote attackers to cause a denial of service via "malicious traffic."
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 confidenceThe vCMP (virtual Clustered Multiprocessing) host component in multiple F5 BIG-IP product lines fails to properly handle malicious traffic, allowing remote unauthenticated attackers to trigger a denial of service condition. The vulnerability affects the hypervisor layer that manages virtual instances, potentially impacting all hosted virtual servers.
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.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.0.0= 11.1.0= 11.2.0= 11.2.1= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.0.0= 11.1.0= 11.2.0= 11.2.1= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.0.0= 11.1.0= 11.2.0= 11.2.1= 11.3.0= 11.0.0= 11.1.0= 11.2.0= 11.2.1= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.0.0= 11.1.0= 11.2.0= 11.2.1= 11.3.0= 11.0.0= 11.1.0= 11.2.0= 11.2.1= 11.3.0= 11.4.0= 11.4.1CVSS 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
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:A/AC:L/Au:N/C:N/I:N/A:C
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.
-
Verify if vCMP is enabledOn the F5 BIG-IP command line, run 'tmsh show vcmp info' or check the vCMP configuration via the web UI under iControl > System > vCMP. Look for the vCMP host and guest status.Affected if vCMP is enabled and running guests - the vulnerability exists in the vCMP hypervisor layer that manages virtual instances.
-
Check the BIG-IP base versionRun 'tmsh show sys version' or 'bigpipe version' from the command line. Alternatively, check the System > Overview page in the web UI.Affected if The installed version matches any of the affected versions listed: 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, or 11.5.3.
-
Identify installed modules and their versionsRun 'tmsh list sys module' to list all installed modules. Check each module's version via 'tmsh show sys module <module-name>' or the web UI under System > Software > Images.Affected if Any of the following modules are installed at the affected versions: Application Acceleration Manager (11.4.0-11.5.3), Global Traffic Manager (11.0.0-11.5.3), Access Policy Manager (11.0.0-11.5.3), Webaccelerator (11.0.0-11.3.0), Application Security Manager (11.0.0-11.5.3), Policy Enforcement Manag
-
Check for vCMP-related crash logsRun 'tmsh show sys crash' or review /var/log/ltm for crash entries related to vCMP host component failures.Affected if Crash logs indicate vCMP host or hypervisor failures that could be related to this vulnerability.
A system is affected if vCMP is enabled and running on a BIG-IP version between 11.0.0 and 11.5.3, particularly with any of the vulnerable modules installed.
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.
From vendor dataUpgrade affected F5 BIG-IP products to version 11.6.0 or later. If immediate upgrading is not feasible, consider restricting network access to the management interface and implementing rate limiting on perimeter devices to reduce attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6546 — 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-2015-6546 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