Bug 1452050 – CVE-2016-10374 perltidy: Uses current working directory without symlink-attack protection

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1452050 - (CVE-2016-10374) CVE-2016-10374 perltidy: Uses current working directory without symlink-attack protection

Summary:	CVE-2016-10374 perltidy: Uses current working directory without symlink-attac...

Status:	CLOSED WONTFIX

Aliases:	CVE-2016-10374

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=low,public=20160813,reported=2...
Keywords:	Security

Depends On:	1452051
Blocks:	1452052
	Show dependency tree / graph

Reported:	2017-05-18 04:48 EDT by Andrej Nemec
Modified:	2017-06-15 03:58 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-06-15 03:56:13 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrej Nemec 2017-05-18 04:48:27 EDT

perltidy relies on the current working directory for certain output files and does not have a symlink-attack protection mechanism, which allows local users to overwrite arbitrary files by creating a symlink, as demonstrated by creating a perltidy.ERR symlink that the victim cannot delete.

References:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862667
http://perltidy.sourceforge.net/ChangeLog.html

Comment 1 Andrej Nemec 2017-05-18 04:49:08 EDT

Created perltidy tracking bugs for this issue:

Affects: fedora-all [bug 1452051]

Comment 2 Dhiru Kholia 2017-06-15 03:58:00 EDT

Statement:

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/ and Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.

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