Menu

Star on GitHub · 3.2k

CVE-2016-7097

4.4 · MEDIUM

The filesystem implementation in the Linux kernel through 4.8.2 preserves the setgid bit during a setxattr call, which allows local users to gain group privileges by leveraging the existence of a s…

Published Oct 16, 2016CWE-285EPSS 0.39%

Overview

CVE-2016-7097 is a medium-severity vulnerability. It was published on October 16, 2016 and has a CVSS 3.0 base score of 4.4 (MEDIUM).

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

Technical description

The filesystem implementation in the Linux kernel through 4.8.2 preserves the setgid bit during a setxattr call, which allows local users to gain group privileges by leveraging the existence of a setgid program with restrictions on execute permissions.

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-7097?

CVE-2016-7097 is a medium-severity vulnerability. It was published on October 16, 2016 and has a CVSS 3.0 base score of 4.4 (MEDIUM).

How severe is CVE-2016-7097?

This vulnerability has a CVSS 3.0 base score of 4.4, 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-7097?

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-7097?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2016-7097 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