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
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: mysql   
(Show other bugs)
Version: 4.0
Hardware: All Linux
Target Milestone: ---
: ---
Assignee: Tom Lane
QA Contact: David Lawrence
Whiteboard: impact=important,public=20050311,sour...
Keywords: Security
Depends On:
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:
Story Points: ---
Clone Of:
Last Closed: 2005-03-28 19:44:44 UTC
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-2005:334 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):

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.


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