Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 85072 - Escape sequence vulnerabilities in hanterm-xf
Escape sequence vulnerabilities in hanterm-xf
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: hanterm-xf (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Joo
Bill Huang
Depends On:
  Show dependency treegraph
Reported: 2003-02-25 06:10 EST by Mark J. Cox
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-08 15:44:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2003:071 normal SHIPPED_LIVE Moderate: hanterm-xf security update 2003-07-08 00:00:00 EDT

  None (edit)
Description Mark J. Cox 2003-02-25 06:10:58 EST
Hangul Terminal provides an escape sequence for reporting the current
window title which essentially takes the current title and places it
directly on the command line. An attacker can craft an escape sequence
that sets the window title of a victim using Hangul Terminal to an
arbitrary command and then report it to the command line. Since it is not
possible to embed a carriage return into the window title the attacker
would then have to convince the victim to press Enter for it to process the
title as a command, although the attacker could craft other escape
sequences that might convince the victim to do so.

It is possible to lock up Hangul Terminal before version 2.0.5 by sending
an invalid DEC UDK escape sequence. 

CAN-2003-0077 CAN-2003-0079
Comment 1 Mark J. Cox 2003-07-08 15:44:19 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


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