CVE-2013-6024: Infoleak

Published 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.

Affected Software

21 affected components
F5 BIG-IP Access Policy Manager=10.1.0
F5 BIG-IP Access Policy Manager=10.2.4
F5 BIG-IP Access Policy Manager=11.0.0
F5 BIG-IP Access Policy Manager=11.1.0
F5 BIG-IP Access Policy Manager=11.2.0
F5 BIG-IP Access Policy Manager=11.2.1
F5 BIG-IP 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=6.0.0
F5 FirePass=6.1.0
F5 FirePass=7.0.0
F5 BIG-IP Access Policy Manager=10.1.0
F5 BIG-IP Access Policy Manager=10.2.4
F5 BIG-IP Access Policy Manager=11.0.0
F5 BIG-IP Access Policy Manager=11.1.0
F5 BIG-IP Access Policy Manager=11.2.0
F5 BIG-IP Access Policy Manager=11.2.1
F5 BIG-IP Access Policy Manager=11.3.0

Event History

Feb 10, 2014
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203