dbcve.org
Big Iq Application Delivery ControllerApplication · F5

CVE-2015-7393

HIGH · 7.4 CVSS v3.0 Published 2016-01-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High
No privileges 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
dcoep in BIG-IP LTM, Analytics, APM, ASM, and Link Controller 11.2.0 through 11.6.0 and 12.0.0 before 12.0.0 HF1, BIG-IP AAM 11.4.0 through 11.6.0 and 12.0.0 before 12.0.0 HF1, BIG-IP AFM and PEM 11.3.0 through 11.6.0 and 12.0.0 before 12.0.0 HF1, BIG-IP DNS 12.0.0 before 12.0.0 HF1, BIG-IP Edge Gateway, WebAccelerator, and WOM 11.2.0 through 11.3.0, BIG-IP GTM 11.2.0 through 11.6.0, BIG-IP PSM 11.2.0 through 11.4.1, Enterprise Manager 3.0.0 through 3.1.1, BIG-IQ Cloud 4.0.0 through 4.5.0, BIG-IQ Device 4.2.0 through 4.5.0, BIG-IQ Security 4.0.0 through 4.5.0, BIG-IQ ADC 4.5.0, BIG-IQ Centralized Management 4.6.0, and BIG-IQ Cloud and Orchestration 1.0.0 allows local users with advanced shell (bash) access to gain privileges via unspecified vectors.

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 · high confidence

This is a local privilege escalation vulnerability in the dcoep component affecting multiple BIG-IP products. An attacker with existing advanced shell (bash) access can leverage unspecified vectors to gain elevated privileges on the affected system.

MitigationApply the vendor-supplied hotfix (12.0.0 HF1 or later for version 12.x; vendor guidance for 11.x). Restrict bash access to only essential administrative personnel and monitor for unauthorized shell access attempts.

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
Big Iq Application Delivery ControllerApplication
Affected:= 4.5.0
Big Ip Application Security ManagerApplication
Affected:= 11.2.0= 11.2.1= 11.3.0= 11.4.0= 11.4.1= 11.5.1= 11.6.0= 12.0.0
Big Iq SecurityApplication
Affected:= 4.0.0= 4.1.0= 4.2.0= 4.3.0= 4.4.0= 4.5.0
Big Ip Wan Optimization ManagerApplication
Affected:= 11.2.0= 11.2.1= 11.3.0
Big Ip Global Traffic ManagerApplication
Affected:= 11.2.1= 11.3.0= 11.4.0= 11.4.1= 11.5.1= 11.6.0
Big Ip Global Traffic Manager11.2.0Application
Affected:all versions
Big Iq Centralized ManagementApplication
Affected:= 4.6.0
Big Ip AnalyticsApplication
Affected:= 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.6.0= 12.0.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
Local
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 checks

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

  1. Identify the F5 product
    Determine which F5 product is installed (e.g., Big IP ASM, Big Iq ADC, Big Ip GTM, Big Ip Analytics, Big Ip WAN Optimization Manager, or Big Iq Centralized Management)
    Affected if The product is any of those listed in the affected products
  2. Determine the installed version
    Use the product's management interface or command line to retrieve the exact version number (e.g., tmsh show version or similar product-specific command)
    Affected if The version matches any of the specific versions listed in the affected products and versions for that product
  3. Check dcoep component presence
    Verify if the dcoep component is installed or running on the system using product-specific diagnostic tools or file system inspection
    Affected if The dcoep component is present and the version matches an affected version
  4. Verify advanced shell access capability
    Confirm whether advanced shell (bash) access is enabled or available for any user accounts on the system
    Affected if bash access exists and the product/version is on the affected list - this is a local privilege escalation requiring existing bash access as a prerequisite

You are affected if you are running any of the listed F5 products at any of the specific versions enumerated in the affected products and versions list, and the dcoep component is present on your system.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied hotfix (12.0.0 HF1 or later for version 12.x; vendor guidance for 11.x). Restrict bash access to only essential administrative personnel and monitor for unauthorized shell access attempts.

Fix this in Big Iq Application Delivery Controller Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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