Skip to content
Fencer Vulns
high 7.2

CVE-2008-4865 json

Untrusted search path vulnerability in valgrind before 3.4.0 allows local users to execute arbitrary programs via a Trojan horse .valgrindr…

published 2008-10-31 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-4844

cvss
7.2
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits
0
none known

Summary

Untrusted search path vulnerability in valgrind before 3.4.0 allows local users to execute arbitrary programs via a Trojan horse .valgrindrc file in the current working directory, as demonstrated using a malicious --db-command options. NOTE: the severity of this issue has been disputed, but CVE is including this issue because execution of a program from an untrusted directory is a common scenario.

Patch / fix

  • valgrind Debian 14, Debian 13, Debian 12 1:3.3.1-3

debian advisories DEBIAN-CVE-2008-4865

  • valgrind RHEL 5 1:3.5.0-1.el5

red hat advisories RHEA-2010:0272

  • valgrind openSUSE Tumbleweed 3.17.0-2.3

opensuse advisories openSUSE-SU-2024:11492-1

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-2008-4865 updated cvss 3.7

valgrind: .valgrindrc loaded from untrusted locations

  • Red Hat Enterprise Linux 4 valgrind
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux (v. 5 server) valgrind 3.5.0-1.el5 Red Hat Enterprise Linux Desktop Workstation (v. 5 client) valgrind 3.5.0-1.el5
    fixed: vendor fix RHEA-2010:0272

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

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

References

Sources

Fencer Vulns 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.