CVE-2013-6024: Infoleak
First published: Mon Feb 10 2014(Updated: )
The Edge Client components in F5 BIG-IP APM 10.x, 11.x, 12.x, 13.x, and 14.x, BIG-IP Edge Gateway 10.x and 11.x, and FirePass 7.0.0 allow attackers to obtain sensitive information from process memory via unspecified vectors.
Credit: cret@cert.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| F5 Access Policy Manager | =10.1.0 | |
| F5 Access Policy Manager | =10.2.4 | |
| F5 Access Policy Manager | =11.0.0 | |
| F5 Access Policy Manager | =11.1.0 | |
| F5 Access Policy Manager | =11.2.0 | |
| F5 Access Policy Manager | =11.2.1 | |
| F5 Access Policy Manager | =11.3.0 | |
| F5 BIG-IP Edge Gateway | =10.1.0 | |
| F5 BIG-IP Edge Gateway | =10.2.4 | |
| F5 BIG-IP Edge Gateway | =11.0.0 | |
| F5 BIG-IP Edge Gateway | =11.5.0 | |
| F5 FirePass SSL VPN | =6.0.0 | |
| F5 FirePass SSL VPN | =6.1.0 | |
| F5 FirePass SSL VPN | =7.0.0 | |
| F5 Access Policy Manager | =10.1.0 | |
| F5 Access Policy Manager | =10.2.4 | |
| F5 Access Policy Manager | =11.0.0 | |
| F5 Access Policy Manager | =11.1.0 | |
| F5 Access Policy Manager | =11.2.0 | |
| F5 Access Policy Manager | =11.2.1 | |
| F5 Access Policy Manager | =11.3.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2013-6024?
CVE-2013-6024 is considered a high severity vulnerability due to its potential to expose sensitive information.
How do I fix CVE-2013-6024?
To fix CVE-2013-6024, it is recommended to apply the latest security patches provided by F5 for the affected versions.
What versions of F5 BIG-IP are affected by CVE-2013-6024?
CVE-2013-6024 affects F5 BIG-IP APM versions 10.x, 11.x, 12.x, 13.x, and 14.x, as well as BIG-IP Edge Gateway and FirePass 7.0.0.
Can CVE-2013-6024 lead to data breaches?
Yes, CVE-2013-6024 can lead to data breaches by allowing attackers to access sensitive information from process memory.
Is there a workaround for CVE-2013-6024?
While a specific workaround is not detailed, the primary mitigation is to upgrade to a patched version of the affected F5 products.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/first-publish-date
- agent/description
- agent/author
- agent/event
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/f5
- canonical/f5 access policy manager
- version/f5 access policy manager/10.1.0
- version/f5 access policy manager/10.2.4
- version/f5 access policy manager/11.0.0
- version/f5 access policy manager/11.1.0
- version/f5 access policy manager/11.2.0
- version/f5 access policy manager/11.2.1
- version/f5 access policy manager/11.3.0
- canonical/f5 big-ip edge gateway
- version/f5 big-ip edge gateway/10.1.0
- version/f5 big-ip edge gateway/10.2.4
- version/f5 big-ip edge gateway/11.0.0
- version/f5 big-ip edge gateway/11.5.0
- canonical/f5 firepass ssl vpn
- version/f5 firepass ssl vpn/6.0.0
- version/f5 firepass ssl vpn/6.1.0
- version/f5 firepass ssl vpn/7.0.0