diff options
author | V3n3RiX <venerix@redcorelinux.org> | 2017-10-09 18:53:29 +0100 |
---|---|---|
committer | V3n3RiX <venerix@redcorelinux.org> | 2017-10-09 18:53:29 +0100 |
commit | 4f2d7949f03e1c198bc888f2d05f421d35c57e21 (patch) | |
tree | ba5f07bf3f9d22d82e54a462313f5d244036c768 /metadata/glsa/glsa-200902-03.xml |
reinit the tree, so we can have metadata
Diffstat (limited to 'metadata/glsa/glsa-200902-03.xml')
-rw-r--r-- | metadata/glsa/glsa-200902-03.xml | 64 |
1 files changed, 64 insertions, 0 deletions
diff --git a/metadata/glsa/glsa-200902-03.xml b/metadata/glsa/glsa-200902-03.xml new file mode 100644 index 000000000000..ad021c251a47 --- /dev/null +++ b/metadata/glsa/glsa-200902-03.xml @@ -0,0 +1,64 @@ +<?xml version="1.0" encoding="utf-8"?> +<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd"> +<glsa id="200902-03"> + <title>Valgrind: Untrusted search path</title> + <synopsis> + An untrusted search path vulnerability in Valgrind might result in the + execution of arbitrary code. + </synopsis> + <product type="ebuild">valgrind</product> + <announced>2009-02-12</announced> + <revised>2009-02-12: 01</revised> + <bug>245317</bug> + <access>local</access> + <affected> + <package name="dev-util/valgrind" auto="yes" arch="*"> + <unaffected range="ge">3.4.0</unaffected> + <vulnerable range="lt">3.4.0</vulnerable> + </package> + </affected> + <background> + <p> + Valgrind is an open-source memory debugger. + </p> + </background> + <description> + <p> + Tavis Ormandy reported that Valgrind loads a .valgrindrc file in the + current working directory, executing commands specified there. + </p> + </description> + <impact type="high"> + <p> + A local attacker could prepare a specially crafted .valgrindrc file and + entice a user to run Valgrind from the directory containing that file, + resulting in the execution of arbitrary code with the privileges of the + user running Valgrind. + </p> + </impact> + <workaround> + <p> + Do not run "valgrind" from untrusted working directories. + </p> + </workaround> + <resolution> + <p> + All Valgrind users should upgrade to the latest version: + </p> + <code> + # emerge --sync + # emerge --ask --oneshot --verbose ">=dev-util/valgrind-3.4.0"</code> + </resolution> + <references> + <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-4865">CVE-2008-4865</uri> + </references> + <metadata tag="requester" timestamp="2009-01-13T17:33:22Z"> + rbu + </metadata> + <metadata tag="submitter" timestamp="2009-01-13T17:46:15Z"> + rbu + </metadata> + <metadata tag="bugReady" timestamp="2009-01-13T17:47:39Z"> + rbu + </metadata> +</glsa> |