CVE-2016-4973 Memory corruption in n/a
Local attackers can exploit buffer overflows in binaries using GCC libssp due to missing Object Size Checking, potentially executing arbitrary code.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2016-4973?
CVE-2016-4973 is a high-severity memory corruption vulnerability in n/a, published on 7 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Weakness: CWE-119
Which versions are affected by CVE-2016-4973?
It affects 1 product.
Products include Gnu Libssp.
How do I fix CVE-2016-4973?
No fix has been published for CVE-2016-4973 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2016-4973 being exploited?
There is no known exploitation of CVE-2016-4973 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2016-4973, ECHO-a343-3595-94e7, GHSA-fxx4-jm8v-4948, UBUNTU-CVE-2016-4973.