Skip to content
Noroxi
CVE-2013-4788· NVD / CVE Program· CNA mitre

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 initial

Noroxi assessment

Priority: Monitor (action score 23/100)

  • Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 11.4% (FIRST EPSS); higher than 95.9% of all records.
  • Special conditions such as timing or configuration are required.
  • Fixed version: glibc (Debian:12) 2.17-94; eglibc (Debian:6.0) 2.11.3-4+deb6u5.

Low priority for now. Upgrade to glibc (Debian:12) 2.17-94; eglibc (Debian:6.0) 2.11.3-4+deb6u5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

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.

MediumCVSS 5.1 · v2.0—Proof of concept Fix available
Published
Oct 4, 2013
Updated
Jun 16, 2026
EPSS
11.4% · 96th percentile

Report tools

JSON

Action score

23

Monitor

Low priority for now.

CVSS
20 / 40 · 5.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 11.4%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2013-4788

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for gnu records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
gnuglibc
gnueglibc

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gnu eglibcall versions
  • gnu glibcup to 2.17 inclusive
  • gnu glibc2.0
  • gnu glibc2.0.1
  • gnu glibc2.0.2
  • gnu glibc2.0.3
  • gnu glibc2.0.4
  • gnu glibc2.0.5
  • gnu glibc2.0.6
  • gnu glibc2.1
  • gnu glibc2.1.1
  • gnu glibc2.1.1.6
  • gnu glibc2.1.2
  • gnu glibc2.1.3
  • gnu glibc2.1.9
  • gnu glibc2.10.1
  • gnu glibc2.11
  • gnu glibc2.11.1
  • gnu glibc2.11.2
  • gnu glibc2.11.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12glibcbefore 2.17-942.17-94
Debian:6.0eglibcbefore 2.11.3-4+deb6u52.11.3-4+deb6u5

Same product

gnu: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-4911Glibc: buffer overflow in ld.so leading to privilege escalationKEV
    80Now
  • CVE-2015-0235Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-depen
    68This week
  • CVE-2015-7547Multiple stack-based buffer overflows in the (1) send_dg and (2) send_vc functions in the libresolv library in the GNU C Library (aka glibc
    59Plan
  • CVE-2024-2961The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converti
    55Plan
  • CVE-2018-11236stdlib/canonicalize.c in the GNU C Library (aka glibc or libc6) 2.27 and earlier, when processing very long pathname arguments to the realpa
    41Plan
  • CVE-2015-8779Stack-based buffer overflow in the catopen function in the GNU C Library (aka glibc or libc6) before 2.23 allows context-dependent attackers
    41Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:eglibc2.11.3-4+deb6u5 · Debian:6.0Package registry (OSV)
debian:glibc2.17-94 · Debian:12Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrylocal2013-09-30

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-5 d
  2. Published
  3. TodayOct 13, 2026+4757 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
P · data can be read
Integrity
P · data or configuration can be modified
Availability
P · the service can be disrupted
Attack complexity
High
Confidentiality impact
P
Integrity impact
P
Availability impact
P

Weakness class (CWE)

CWE-20 · Improper Input Validation

CVSS vector

AV:N/AC:H/Au:N/C:P/I:P/A:P

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records