CVE-2013-4788
Public on
Last Modified:
Insights vulnerability analysis
Description
The CVE Program describes this issue as:
The PTR_MANGLE implementation in the GNU C Library (aka glibc or libc6) 2.4, 2.17, and earlier, and Embedded GLIBC (EGLIBC) does not initialize the random value for the pointer guard, which makes it easier for context-dependent attackers to control execution flow by leveraging a buffer-overflow vulnerability in an application and using the known zero value pointer guard to calculate a pointer address.
Statement
Red Hat Security Response Team has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates for Red Hat Enterprise Linux 5 and 6. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ .
Additional information
- Bugzilla 985625: glibc: PTR_MANGLE does not initialize to a random value for the pointer guard when compiling static executables
- FAQ: Frequently asked questions about CVE-2013-4788
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
| Red Hat | NVD | |
|---|---|---|
CVSS v2 Base Score | 3.7 | 5.1 |
Attack Vector | Local | Network |
Access Complexity | High | High |
Authentication | None | None |
Confidentiality Impact | Partial | Partial |
Integrity Impact | Partial | Partial |
Availability Impact | Partial | Partial |
CVSS v2 Vector
Red Hat: AV:L/AC:H/Au:N/C:P/I:P/A:P
NVD: AV:N/AC:H/Au:N/C:P/I:P/A:P
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
What can I do if my product is listed as "Will not fix"?
What can I do if my product is listed as "Fix deferred"?
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
