CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in GCC for Stack Smashing Protection. Affected by this issue is some unknown functionality of the component libssp. The manipulation leads to memory corruption. This vulnerability is handled as CVE-2016-4973. The attack needs to be approached locally. There is no exploit available. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability classified as problematic was found in GCC for Stack Smashing Protection (unknown version). Affected by this vulnerability is an unknown code block of the component libssp. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Binaries compiled against targets that use the libssp library in GCC for stack smashing protection (SSP) might allow local users to perform buffer overflow attacks by leveraging lack of the Object Size Checking feature.
The bug was discovered 08/17/2017. The weakness was shared 06/07/2017 by Yaakov Selkowitz with Red Hat (oss-sec). It is possible to read the advisory at openwall.com. This vulnerability is known as CVE-2016-4973 since 05/24/2016. The exploitation appears to be easy. Attacking locally is a requirement. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 92530†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/24/2016 🔍08/17/2016 🔍
06/07/2017 🔍
06/07/2017 🔍
06/08/2017 🔍
08/17/2017 🔍
10/14/2019 🔍
Sources
Advisory: openwall.comResearcher: Yaakov Selkowitz
Organization: Red Hat
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-4973 (🔍)
GCVE (CVE): GCVE-0-2016-4973
GCVE (VulDB): GCVE-100-102079
SecurityFocus: 92530 - GNU GCC CVE-2016-4973 Local Security Bypass Vulnerability
Entry
Created: 06/08/2017 08:34Updated: 10/14/2019 16:04
Changes: 06/08/2017 08:34 (60), 10/14/2019 16:04 (1)
Complete: 🔍
Cache ID: 216:A69:103
No comments yet. Languages: en.
Please log in to comment.