Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2011-1658


ld.so in the GNU C Library (aka glibc or libc6) 2.13 and earlier expands the $ORIGIN dynamic string token when RPATH is composed entirely of this token, which might allow local users to gain privileges by creating a hard link in an arbitrary directory to a (1) setuid or (2) setgid program with this RPATH value, and then executing the program with a crafted value for the LD_PRELOAD environment variable, a different vulnerability than CVE-2010-3847 and CVE-2011-0536. NOTE: it is not expected that any standard operating-system distribution would ship an applicable setuid or setgid program.


Security Impact Summary

CVE-2011-1658 is a security vulnerability that . Impacting 1 product from gnu organizations running these solutions should prioritize assessment and patching.

Historical Context

Documented in 2011, this vulnerability occurred amid the cloud computing expansion era, where traditional network perimeter security models were being reevaluated. Organizations were transitioning from isolated infrastructure to interconnected systems, creating new attack surfaces that vulnerabilities like this could exploit.


Published

2011-04-08T15:17:28.493

Last Modified

2025-04-11T00:51:21.963

Status

Deferred

Source

[email protected]

Severity

CVSSv2: 3.7 (LOW)

CVSSv2 Vector

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

  • Access Vector: LOCAL
  • Access Complexity: HIGH
  • Authentication: NONE
  • Confidentiality Impact: PARTIAL
  • Integrity Impact: PARTIAL
  • Availability Impact: PARTIAL
Exploitability Score

1.9

Impact Score

6.4

Weaknesses
  • Type: Primary
    CWE-264

Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Application gnu glibc ≤ 2.13 Yes
Application gnu glibc 1.00 Yes
Application gnu glibc 1.01 Yes
Application gnu glibc 1.02 Yes
Application gnu glibc 1.03 Yes
Application gnu glibc 1.04 Yes
Application gnu glibc 1.05 Yes
Application gnu glibc 1.06 Yes
Application gnu glibc 1.07 Yes
Application gnu glibc 1.08 Yes
Application gnu glibc 1.09 Yes
Application gnu glibc 1.09.1 Yes
Application gnu glibc 2.0 Yes
Application gnu glibc 2.0.1 Yes
Application gnu glibc 2.0.2 Yes
Application gnu glibc 2.0.3 Yes
Application gnu glibc 2.0.4 Yes
Application gnu glibc 2.0.5 Yes
Application gnu glibc 2.0.6 Yes
Application gnu glibc 2.1 Yes
Application gnu glibc 2.1.1 Yes
Application gnu glibc 2.1.1.6 Yes
Application gnu glibc 2.1.2 Yes
Application gnu glibc 2.1.3 Yes
Application gnu glibc 2.1.3.10 Yes
Application gnu glibc 2.1.9 Yes
Application gnu glibc 2.2 Yes
Application gnu glibc 2.2.1 Yes
Application gnu glibc 2.2.2 Yes
Application gnu glibc 2.2.3 Yes
Application gnu glibc 2.2.4 Yes
Application gnu glibc 2.2.5 Yes
Application gnu glibc 2.3 Yes
Application gnu glibc 2.3.1 Yes
Application gnu glibc 2.3.2 Yes
Application gnu glibc 2.3.3 Yes
Application gnu glibc 2.3.4 Yes
Application gnu glibc 2.3.5 Yes
Application gnu glibc 2.3.6 Yes
Application gnu glibc 2.3.10 Yes
Application gnu glibc 2.4 Yes
Application gnu glibc 2.5 Yes
Application gnu glibc 2.5.1 Yes
Application gnu glibc 2.6 Yes
Application gnu glibc 2.6.1 Yes
Application gnu glibc 2.7 Yes
Application gnu glibc 2.8 Yes
Application gnu glibc 2.9 Yes
Application gnu glibc 2.10 Yes
Application gnu glibc 2.10.1 Yes
Application gnu glibc 2.10.2 Yes
Application gnu glibc 2.11 Yes
Application gnu glibc 2.11.1 Yes
Application gnu glibc 2.11.2 Yes
Application gnu glibc 2.11.3 Yes
Application gnu glibc 2.12.0 Yes
Application gnu glibc 2.12.1 Yes
Application gnu glibc 2.12.2 Yes

References

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For gnu's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.