Bug 150868 - CAN-2005-0711 Insecure temporary file creation with CREATE TEMPORARY TABLE
Summary: CAN-2005-0711 Insecure temporary file creation with CREATE TEMPORARY TABLE
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: mysql
Version: 4.0
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Tom Lane
QA Contact: David Lawrence
URL:
Whiteboard: impact=important,public=20050311,sour...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-11 15:30 UTC by Tom Lane
Modified: 2013-07-03 03:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-03-28 19:44:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:334 0 normal SHIPPED_LIVE Important: mysql security update 2005-03-28 05:00:00 UTC

Description Tom Lane 2005-03-11 15:30:53 UTC 
Description of problem:
If an authenticated user has CREATE TEMPORARY TABLE privileges on any
existent database, a symlink attack is possible. 

Reported to vulnwatch.org by Stefano Di Paola on 11 Mar 2005

Version-Release number of selected component (if applicable):
mysql-4.1.7-5.RHEL4.1

How reproducible:
Requires some luck to guess name that will be used for temp file,
but unfortunately that's fairly predictable.

Steps to Reproduce:
1.  See vulnwatch report.

Additional info:
This is fixed in 4.1.10a, which we should upgrade to anyway as it
contains numerous other bug fixes.
Comment 1 Josh Bressers 2005-03-28 19:44:44 UTC 
An advisory 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.

http://rhn.redhat.com/errata/RHSA-2005-334.html
Note You need to log in before you can comment on or make changes to this bug.