Bug 639869 – CVE-2011-0012 spice-xpi: symlink attack on usbrdrctl log file

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 639869 - (CVE-2011-0012) CVE-2011-0012 spice-xpi: symlink attack on usbrdrctl log file

Summary:	CVE-2011-0012 spice-xpi: symlink attack on usbrdrctl log file

Status:	CLOSED ERRATA

Aliases:	CVE-2011-0012

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	public=20110407,reported=20101004,sou...
Keywords:	Security

Depends On:	639870 639871
Blocks:
	Show dependency tree / graph

Reported:	2010-10-04 05:06 EDT by Petr Matousek
Modified:	2015-08-19 04:56 EDT (History)
CC List:	11 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2012-02-27 10:17:31 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2011:0426	normal	SHIPPED_LIVE	Moderate: spice-xpi security update	2011-04-07 18:19:56 EDT

Groups: None (edit)

Description Petr Matousek 2010-10-04 05:06:17 EDT

Spice-xpi uses predictable name for usbrdrctl log file which a malicious user could use to overwrite arbitrary files via a symlink attack, with the privileges of the user running spice-xpi.

Comment 2 errata-xmlrpc 2011-04-07 18:20:02 EDT

This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2011:0426 https://rhn.redhat.com/errata/RHSA-2011-0426.html

Comment 3 Peter Hatina 2012-02-27 10:17:31 EST

This bug has been fixed almost a year ago, closing.

Note You need to log in before you can comment on or make changes to this bug.