CVE-2008-1951
Description
From CVE.org
Untrusted search path vulnerability in a certain Red Hat build script for Standards Based Linux Instrumentation for Manageability (sblim) libraries before 1-13a.el4_6.1 in Red Hat Enterprise Linux (RHEL) 4, and before 1-31.el5_2.1 in RHEL 5, allows local users to gain privileges via a malicious library in a certain subdirectory of /var/tmp, related to an incorrect RPATH setting, as demonstrated by a malicious libc.so library for tog-pegasus.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v2 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.2 | 4.6 | N/A |
| Attack Vector | Local | Local | N/A |
| Access Complexity | Low | Low | N/A |
| Authentication | None | None | N/A |
| Confidentiality Impact | Complete | Partial | N/A |
| Integrity Impact | Complete | Partial | N/A |
| Availability Impact | Complete | Partial | N/A |
Vector
Red Hat: AV:L/AC:L/Au:N/C:C/I:C/A:C
NVD: AV:L/AC:L/Au:N/C:P/I:P/A:P
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability,Access Control
Technical Impact: Gain Privileges or Assume Identity; Execute Unauthorized Code or Commands
There is the potential for arbitrary code execution with privileges of the vulnerable program. If the product uses a search path to locate critical resources such as programs or libraries, then an attacker could modify that search path to point to a malicious program/library, which the targeted product would then execute.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
The program could be redirected to the wrong files, potentially triggering a crash or hang when the targeted file is too large or does not have the expected format.
Confidentiality
Technical Impact: Read Files or Directories
The program could access unauthorized data and send the output of unauthorized files to the attacker.
Other
Technical Impact: Varies by Context
The problem extends to any type of critical resource that the product trusts. For example, the attacker could modify configuration in unexpected ways.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.