Skip to content
Noroxi
CVE-2010-3847· NVD / CVE Program· CNA redhat

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

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.

MediumCVSS 6.9 · v2.0—Weaponized Fix available
Published
Jan 7, 2011
Updated
Jun 16, 2026
EPSS
9.5% · 95th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
27 / 40 · 6.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 9.5%

Affected systems

VendorProduct
gnuglibc

Affected versions

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

  • gnu glibcup to 2.11.2 inclusive
  • gnu glibc1.00
  • gnu glibc1.01
  • gnu glibc1.02
  • gnu glibc1.03
  • gnu glibc1.04
  • gnu glibc1.05
  • gnu glibc1.06
  • gnu glibc1.07
  • gnu glibc1.08
  • gnu glibc1.09
  • gnu glibc1.09.1
  • 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

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12glibcbefore 2.11.2-82.11.2-8
Debian:5.0glibcbefore 2.7-18lenny62.7-18lenny6
Debian:5.0glibcbefore 2.7-18lenny72.7-18lenny7
Red Hat:enterprise_linux:5::clientglibcbefore 0:2.5-49.el5_5.60:2.5-49.el5_5.6
Red Hat:enterprise_linux:5::clientglibc-commonbefore 0:2.5-49.el5_5.60:2.5-49.el5_5.6
Red Hat:enterprise_linux:5::clientglibc-debuginfobefore 0:2.5-49.el5_5.60:2.5-49.el5_5.6
Red Hat:enterprise_linux:5::clientglibc-debuginfo-commonbefore 0:2.5-49.el5_5.60:2.5-49.el5_5.6
Red Hat:enterprise_linux:5::clientglibc-develbefore 0:2.5-49.el5_5.60:2.5-49.el5_5.6
Red Hat:enterprise_linux:5::clientglibc-headersbefore 0:2.5-49.el5_5.60:2.5-49.el5_5.6
Red Hat:enterprise_linux:5::clientglibc-utilsbefore 0:2.5-49.el5_5.60:2.5-49.el5_5.6
Red Hat:enterprise_linux:5::clientnscdbefore 0:2.5-49.el5_5.60:2.5-49.el5_5.6
Red Hat:enterprise_linux:6::clientglibcbefore 0:2.12-1.7.el6_0.30:2.12-1.7.el6_0.3
Red Hat:enterprise_linux:6::clientglibc-commonbefore 0:2.12-1.7.el6_0.30:2.12-1.7.el6_0.3
Red Hat:enterprise_linux:6::clientglibc-debuginfobefore 0:2.12-1.7.el6_0.30:2.12-1.7.el6_0.3
Red Hat:enterprise_linux:6::clientglibc-develbefore 0:2.12-1.7.el6_0.30:2.12-1.7.el6_0.3
Red Hat:enterprise_linux:6::clientglibc-headersbefore 0:2.12-1.7.el6_0.30:2.12-1.7.el6_0.3
Red Hat:enterprise_linux:6::clientglibc-staticbefore 0:2.12-1.7.el6_0.30:2.12-1.7.el6_0.3
Red Hat:enterprise_linux:6::clientglibc-utilsbefore 0:2.12-1.7.el6_0.30:2.12-1.7.el6_0.3
Red Hat:enterprise_linux:6::clientnscdbefore 0:2.12-1.7.el6_0.30:2.12-1.7.el6_0.3

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
    85Now
  • 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:glibc2.11.2-8 · Debian:12Package registry (OSV)
red hat:glibc0:2.5-49.el5_5.6 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:glibc-common0:2.5-49.el5_5.6 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:glibc-debuginfo0:2.5-49.el5_5.6 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:glibc-debuginfo-common0:2.5-49.el5_5.6 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:glibc-devel0:2.5-49.el5_5.6 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:glibc-headers0:2.5-49.el5_5.6 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:glibc-static0:2.12-1.7.el6_0.3 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:glibc-utils0:2.5-49.el5_5.6 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)
red hat:nscd0:2.5-49.el5_5.6 · Red Hat:enterprise_linux:5::clientPackage registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×2
  • Exploit-DB entry ×6
  • Proof-of-concept repository on GitHub ×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 entrylocal2018-02-12
Exploit-DB entrylocal2018-02-12
Exploit-DB entrylocal2018-02-12
Exploit-DB entrylocal2018-02-12
Exploit-DB entrylocal2010-10-22
Exploit-DB entrylocal2010-10-18
Metasploit moduleexploit/linux/local/glibc_ld_audit_dso_load_priv_escglibc LD_AUDIT Arbitrary DSO Load Privilege Escalationexploit2010-10-18
Metasploit moduleexploit/linux/local/glibc_origin_expansion_priv_escglibc '$ORIGIN' Expansion Privilege Escalationexploit2010-10-18
Proof-of-concept repository on GitHubstars:02017-01-02

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-82 d
  2. Metasploit-82 d
  3. Published
  4. TodaySep 30, 2026+5745 d
EPSS, last 120 days+1% in 7 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.

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

    If successful

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

    CVSS vector

    AV:L/AC:M/Au:N/C:C/I:C/A:C

    nvd-primary

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

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

    References

    All records