Bug 798353 (CVE-2012-1095) - CVE-2012-1095 osc: Improper sanitization of terminal emulator escape sequences when displaying build log and build status
Summary: CVE-2012-1095 osc: Improper sanitization of terminal emulator escape sequence...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: CVE-2012-1095
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 799226 799227
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-28 17:50 UTC by Jan Lieskovsky
Modified: 2019-09-29 12:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-18 07:04:06 UTC


Attachments (Terms of Use)

Description Jan Lieskovsky 2012-02-28 17:50:48 UTC
A security flaw was found in the way osc, the Python language based command line client for the openSUSE build service, displayed build logs and build status for particular build. A rogue repository server could use this flaw to modify window's title, or possibly execute arbitrary commands or overwrite files via a specially-crafted build log or build status output containing an escape sequence for a terminal emulator.

References:
[1] https://bugzilla.novell.com/show_bug.cgi?id=749335

Comment 1 Jan Lieskovsky 2012-02-28 17:57:53 UTC
CVE request:
[2] http://www.openwall.com/lists/oss-security/2012/02/28/9

Comment 2 Jan Lieskovsky 2012-03-02 07:45:42 UTC
The CVE identifier of CVE-2012-1095 has been assigned to this issue:
[3] http://www.openwall.com/lists/oss-security/2012/03/02/2

Comment 3 Jan Lieskovsky 2012-03-02 07:47:30 UTC
Once there is final upstream patch, please schedule updates for the versions, of the osc package, as shipped with Fedora 15, Fedora 16 and Fedora EPEL 6.

Comment 4 Jan Lieskovsky 2012-03-02 07:49:19 UTC
Created osc tracking bugs for this issue

Affects: fedora-all [bug 799226]
Affects: epel-6 [bug 799227]


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