dbcve.org
Big Iq SecurityApplication · F5

CVE-2015-3628

HIGH · 9.0 CVSS v2.0 Published 2015-12-07
No fix yet
No fix has been published. The vendor has not shipped a fixed release or patch. You remain exposed.
See remediation →
96/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable 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
The iControl API in F5 BIG-IP LTM, AFM, Analytics, APM, ASM, Link Controller, and PEM 11.3.0 before 11.5.3 HF2 and 11.6.0 before 11.6.0 HF6, BIG-IP AAM 11.4.0 before 11.5.3 HF2 and 11.6.0 before 11.6.0 HF6, BIG-IP Edge Gateway, WebAccelerator, and WOM 11.3.0, BIG-IP GTM 11.3.0 before 11.6.0 HF6, BIG-IP PSM 11.3.0 through 11.4.1, Enterprise Manager 3.1.0 through 3.1.1, BIG-IQ Cloud and Security 4.0.0 through 4.5.0, BIG-IQ Device 4.2.0 through 4.5.0, and BIG-IQ ADC 4.5.0 allows remote authenticated users with the "Resource Administrator" role to gain privileges via an iCall (1) script or (2) handler in a SOAP request to iControl/iControlPortal.cgi.

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
How this class of weakness works · CWE-264

A legacy NVD category covering weaknesses where permissions or privileges are assigned, checked, or dropped incorrectly, so an action ends up running with more access than it should. It is an umbrella label from older records, not a single flaw. The remedy depends on the specific case, but the throughline is least privilege with explicit, checked transitions wherever privilege changes.

General guidance for the permissions, privileges & access controls class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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 Iq SecurityApplication
Affected:= 4.0.0= 4.1.0= 4.2.0= 4.3.0= 4.4.0= 4.5.0
Big Ip Application Acceleration ManagerApplication
Affected:= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.6.0
Big Ip Wan Optimization ManagerApplication
Affected:= 11.3.0
Big Iq AdcApplication
Affected:= 4.5.0
Big Ip Application Security ManagerApplication
Affected:= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.6.0
Big Ip Global Traffic ManagerApplication
Affected:= 11.3.0= 11.4.0= 11.4.1= 11.5.0= 11.5.1= 11.5.2= 11.5.3= 11.6.0
Big Iq DeviceApplication
Affected:= 4.2.0= 4.3.0= 4.4.0= 4.5.0
Big Ip Edge GatewayWeb browser
Affected:= 11.3.0

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
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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
Recommended fix High confidence

BIG-IP 11.5.3 HF2 or 11.6.0 HF6 (or later); BIG-IQ 4.5.1 or later

  1. 1. Identify the exact BIG-IP/BIG-IQ product, version, and module (LTM, ASM, GTM, etc.) currently installed
  2. 2. For BIG-IP LTM, AFM, Analytics, APM, ASM, Link Controller, PEM: upgrade to 11.5.3 HF2 or later, or 11.6.0 HF6 or later
  3. 3. For BIG-IP AAM: upgrade to 11.5.3 HF2 or later, or 11.6.0 HF6 or later
  4. 4. For BIG-IP GTM: upgrade to 11.6.0 HF6 or later
  5. 5. For BIG-IP PSM (11.3.0-11.4.1): upgrade to a supported version (PSM was deprecated; migrate to newer BIG-IP version)
  6. 6. For BIG-IP Edge Gateway, WebAccelerator, WOM 11.3.0: upgrade to 11.5.3 HF2 or later, or 11.6.0 HF6 or later
  7. 7. For Enterprise Manager 3.1.0-3.1.1: upgrade to latest supported version or migrate to BIG-IQ
  8. 8. For BIG-IQ Cloud and Security 4.0.0-4.5.0: upgrade to 4.5.1 or later if available, or migrate to newer BIG-IQ version
Caveat Hotfix upgrades may have compatibility implications with other installed components; always test in non-production environment first

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

No vendor fix exists Big Iq Security has not published a patch for this.

There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.

Add your voice

Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.

Can’t wait

We develop and verify an original fix where the vendor hasn’t, from $1,950. Deployed to your staging first — never straight to production.

Scope it with us

See what else the community needs solved on the solutions-needed board.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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