Skip to content
Fencer Intel
medium 6.9

CVE-2010-3847 json

elf/dl-load.c in ld.so in the GNU C Library (aka glibc or libc6) through 2.11.2, and 2.12.x through 2.12.1, does not properly handle a valu…

published 15y ago modified 4mo ago also EUVD-2010-3826

cvss
6.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.3%
EPSS 10.3% chance of exploitation in 30 days, percentile 95%
public exploits
6
Metasploit and Exploit-DB

Summary

elf/dl-load.c in ld.so in the GNU C Library (aka glibc or libc6) through 2.11.2, and 2.12.x through 2.12.1, does not properly handle a value of $ORIGIN for the LD_AUDIT environment variable, which allows local users to gain privileges via a crafted dynamic shared object (DSO) located in an arbitrary directory.

Patch / fix

  • glibc Debian 14, Debian 13, Debian 12 2.11.2-8

debian advisories DEBIAN-CVE-2010-3847

  • glibc RHEL 6 2.12-1.7.el6_0.3
  • nscd RHEL 6 2.12-1.7.el6_0.3
  • glibc-utils RHEL 6 2.12-1.7.el6_0.3
  • glibc-common RHEL 6 2.12-1.7.el6_0.3
  • glibc RHEL 5 2.5-49.el5_5.6
  • nscd RHEL 5 2.5-49.el5_5.6
  • glibc-utils RHEL 5 2.5-49.el5_5.6
  • glibc-common RHEL 5 2.5-49.el5_5.6

red hat advisories RHSA-2010:0872RHSA-2010:0787

Is CVE-2010-3847 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-3847 updated cvss 7.2

glibc: ld.so insecure handling of $ORIGIN in LD_AUDIT for setuid/setgid programs

  • Red Hat Enterprise Linux (v. 5 server) nscd 2.5-49.el5_5.6, glibc 2.5-49.el5_5.6, glibc-utils 2.5-49.el5_5.6, glibc-common 2.5-49.el5_5.6, glibc-debuginfo-common 2.5-49.el5_5.6 Red Hat Enterprise Linux Desktop (v. 5 client) nscd 2.5-49.el5_5.6, glibc 2.5-49.el5_5.6, glibc-utils 2.5-49.el5_5.6, glibc-common 2.5-49.el5_5.6, glibc-debuginfo-common 2.5-49.el5_5.6
    fixed: vendor fix RHSA-2010:0787
  • Red Hat Enterprise Linux Desktop (v. 6) nscd 2.12-1.7.el6_0.3, glibc 2.12-1.7.el6_0.3, glibc-utils 2.12-1.7.el6_0.3, glibc-common 2.12-1.7.el6_0.3 Red Hat Enterprise Linux Desktop Optional (v. 6) nscd 2.12-1.7.el6_0.3, glibc 2.12-1.7.el6_0.3, glibc-utils 2.12-1.7.el6_0.3, glibc-common 2.12-1.7.el6_0.3 Red Hat Enterprise Linux HPC Node (v. 6) nscd 2.12-1.7.el6_0.3, glibc 2.12-1.7.el6_0.3, glibc-utils 2.12-1.7.el6_0.3, glibc-common 2.12-1.7.el6_0.3 Red Hat Enterprise Linux HPC Node Optional (v. 6) nscd 2.12-1.7.el6_0.3, glibc 2.12-1.7.el6_0.3, glibc-utils 2.12-1.7.el6_0.3, glibc-common 2.12-1.7.el6_0.3 Red Hat Enterprise Linux Server (v. 6) nscd 2.12-1.7.el6_0.3, glibc 2.12-1.7.el6_0.3, glibc-utils 2.12-1.7.el6_0.3, glibc-common 2.12-1.7.el6_0.3 Red Hat Enterprise Linux Server Optional (v. 6) nscd 2.12-1.7.el6_0.3, glibc 2.12-1.7.el6_0.3, glibc-utils 2.12-1.7.el6_0.3, glibc-common 2.12-1.7.el6_0.3
    +2 more products
    Red Hat Enterprise Linux Workstation (v. 6) nscd 2.12-1.7.el6_0.3, glibc 2.12-1.7.el6_0.3, glibc-utils 2.12-1.7.el6_0.3, glibc-common 2.12-1.7.el6_0.3 Red Hat Enterprise Linux Workstation Optional (v. 6) nscd 2.12-1.7.el6_0.3, glibc 2.12-1.7.el6_0.3, glibc-utils 2.12-1.7.el6_0.3, glibc-common 2.12-1.7.el6_0.3
    fixed: vendor fix RHSA-2010:0872

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (Metasploit exploit/linux/local/glibc_ld_audit_dso_load_priv_esc)
  2. Published

Exploit prediction

10.34% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 2.0 6.9 AV:L/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.