summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'metadata/glsa/glsa-200510-02.xml')
-rw-r--r--metadata/glsa/glsa-200510-02.xml70
1 files changed, 70 insertions, 0 deletions
diff --git a/metadata/glsa/glsa-200510-02.xml b/metadata/glsa/glsa-200510-02.xml
new file mode 100644
index 000000000000..f6a2418b1487
--- /dev/null
+++ b/metadata/glsa/glsa-200510-02.xml
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
+<glsa id="200510-02">
+ <title>Berkeley MPEG Tools: Multiple insecure temporary files</title>
+ <synopsis>
+ The Berkeley MPEG Tools use temporary files in various insecure ways,
+ potentially allowing a local user to overwrite arbitrary files.
+ </synopsis>
+ <product type="ebuild">MPEG Tools</product>
+ <announced>2005-10-03</announced>
+ <revised count="01">2005-10-03</revised>
+ <bug>107344</bug>
+ <access>local</access>
+ <affected>
+ <package name="media-video/mpeg-tools" auto="yes" arch="*">
+ <unaffected range="ge">1.5b-r2</unaffected>
+ <vulnerable range="lt">1.5b-r2</vulnerable>
+ </package>
+ </affected>
+ <background>
+ <p>
+ The Berkeley MPEG Tools are a collection of utilities for
+ manipulating MPEG video technology, including an encoder (mpeg_encode)
+ and various conversion utilities.
+ </p>
+ </background>
+ <description>
+ <p>
+ Mike Frysinger of the Gentoo Security Team discovered that
+ mpeg_encode and the conversion utilities were creating temporary files
+ with predictable or fixed filenames. The 'test' make target of the MPEG
+ Tools also relied on several temporary files created insecurely.
+ </p>
+ </description>
+ <impact type="normal">
+ <p>
+ A local attacker could create symbolic links in the temporary
+ files directory, pointing to a valid file somewhere on the filesystem.
+ When the utilities are executed (or 'make test' is run), this would
+ result in the file being overwritten with the rights of the user
+ running the command.
+ </p>
+ </impact>
+ <workaround>
+ <p>
+ There is no known workaround at this time.
+ </p>
+ </workaround>
+ <resolution>
+ <p>
+ All Berkeley MPEG Tools users should upgrade to the latest
+ version:
+ </p>
+ <code>
+ # emerge --sync
+ # emerge --ask --oneshot --verbose "&gt;=media-video/mpeg-tools-1.5b-r2"</code>
+ </resolution>
+ <references>
+ <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-3115">CAN-2005-3115</uri>
+ </references>
+ <metadata tag="requester" timestamp="2005-09-30T07:41:47Z">
+ koon
+ </metadata>
+ <metadata tag="bugReady" timestamp="2005-10-01T09:55:55Z">
+ koon
+ </metadata>
+ <metadata tag="submitter" timestamp="2005-10-02T13:13:54Z">
+ koon
+ </metadata>
+</glsa>