CVE-2018-5516 json
On F5 BIG-IP 13.0.0-13.1.0.5, 12.1.0-12.1.2, or 11.2.1-11.6.3.1, Enterprise Manager 3.1.1, BIG-IQ Centralized Management 5.0.0-5.4.0 or 4.6…
published 2018-05-02 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-17285
- cvss
- 4.7
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
On F5 BIG-IP 13.0.0-13.1.0.5, 12.1.0-12.1.2, or 11.2.1-11.6.3.1, Enterprise Manager 3.1.1, BIG-IQ Centralized Management 5.0.0-5.4.0 or 4.6.0, BIG-IQ Cloud and Orchestration 1.0.0, or F5 iWorkflow 2.0.2-2.3.0, authenticated users granted TMOS Shell (tmsh) access can access objects on the file system which would normally be disallowed by tmsh restrictions. This allows for authenticated, low privileged attackers to exfiltrate objects on the file system which should not be allowed.
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 4.7 | CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.7 | AV:L/AC:M/Au:N/C:C/I:N/A:N |
Affected products
- F5 Networks, Inc. BIG-IP (LTM, AAM, AFM, Analytics, APM, ASM, DNS, Edge Gateway, GTM, Link Controller, PEM, WebAccelerator, WebSafe)
- F5 Networks, Inc. Enterprise Manager
- F5 Networks, Inc. BIG-IQ Centralized Management
- F5 Networks, Inc. BIG-IQ Cloud and Orchestration
- F5 Networks, Inc. iWorkflow
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
References
-
support.f5.com
/csp/article/K37442533
vendor-advisory
-
securitytracker.com
/id/1040800
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1040799
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-5516
- NVD CVE-2018-5516
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.