Menu

Star on GitHub · 3.2k

CVE-2016-6249

5.3 · MEDIUM

F5 BIG-IP 12.0.0 and 11.5.0 - 11.6.1 REST requests which timeout during user account authentication may log sensitive attributes such as passwords in plaintext to /var/log/restjavad.0.log.

Published Feb 20, 2017CWE-200EPSS 0.33%

Overview

CVE-2016-6249 is a medium-severity vulnerability. It was published on February 20, 2017 and has a CVSS 3.0 base score of 5.3 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 5.3, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

F5 BIG-IP 12.0.0 and 11.5.0 - 11.6.1 REST requests which timeout during user account authentication may log sensitive attributes such as passwords in plaintext to /var/log/restjavad.0.log. It may allow local users to obtain sensitive information by reading these files.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2016-6249?

CVE-2016-6249 is a medium-severity vulnerability. It was published on February 20, 2017 and has a CVSS 3.0 base score of 5.3 (MEDIUM).

How severe is CVE-2016-6249?

This vulnerability has a CVSS 3.0 base score of 5.3, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2016-6249?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2016-6249?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-6249 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2016

View all