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 98924 - CAN-2003-0539 ddskk temporary file vulnerability
CAN-2003-0539 ddskk temporary file vulnerability
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: ddskk (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jens Petersen
Bill Huang
: Security
: 100419 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2003-07-10 10:31 EDT 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-08-11 03:24:20 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:241 normal SHIPPED_LIVE : Updated ddskk packages fix temporary file vulnerability 2003-08-11 00:00:00 EDT
Red Hat Product Errata RHSA-2003:242 normal SHIPPED_LIVE Low: ddskk security update 2003-08-11 00:00:00 EDT

  None (edit)
Description Mark J. Cox 2003-07-10 10:31:20 EDT
ddskk is a simple Kana to Kanji conversion program for Emacs.  ddskk has a
temporary file creation vulnerability allowing overwriting of arbitrary files as
the user running ddskk.
Comment 1 Mark J. Cox 2003-07-22 05:06:11 EDT
*** Bug 100419 has been marked as a duplicate of this bug. ***
Comment 2 Mark J. Cox 2003-07-29 14:16:52 EDT
RHSA-2003:242 currently awaiting testing
Comment 3 Mark J. Cox 2003-08-11 03:24:20 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.