CVE-2013-4788

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

11.4% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2013-10-04 17:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:57 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 11.4% in the next 30 days (EPSS).
• Severity: 5.1 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2013-10-04 17:55 UTC

Last modified

2026-06-16 23:57 UTC

Exploit probability

11.4% · EPSS, next 30 days

Weakness

CWE-20 · Improper input validation

Record status

Modified

Affected

• Gnu Glibc ≤ 2.17
• Gnu Glibc 2.0
• Gnu Glibc 2.0.1
• Gnu Glibc 2.0.2
• Gnu Glibc 2.0.3
• Gnu Glibc 2.0.4
• Gnu Glibc 2.0.5
• Gnu Glibc 2.0.6

Attack profile CVSS 2.0 · 5.1

Attack vector

Network

Complexity

High

Authentication

None

Confidentiality

Partial

Integrity

Partial

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2013-4788.md and follow it. Check whether this project is affected by CVE-2013-4788. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge