Bug 1480330 (CVE-2017-1000115) - CVE-2017-1000115 Mercurial: pathaudit: path traversal via symlink
Summary: CVE-2017-1000115 Mercurial: pathaudit: path traversal via symlink
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2017-1000115
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1479968 1479969 1480454
Blocks: 1480327
TreeView+ depends on / blocked
 
Reported: 2017-08-10 17:41 UTC by Cedric Buissart 🐶
Modified: 2019-09-29 14:18 UTC (History)
4 users (show)

Fixed In Version: mercurial 4.3, mercurial 4.2.3
Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in the way Mercurial handles path auditing and caches the results. An attacker could abuse a repository with a series of commits mixing symlinks and regular files/directories to trick Mercurial into writing outside of a given repository.
Clone Of:
Environment:
Last Closed: 2017-08-18 08:17:52 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2489 normal SHIPPED_LIVE Important: mercurial security update 2017-08-17 15:06:19 UTC

Description Cedric Buissart 🐶 2017-08-10 17:41:27 UTC
The symlink auditor is sometimes cached too long, and can be confused into allowing write access to outside the repo.

Comment 3 Cedric Buissart 🐶 2017-08-10 19:37:02 UTC
External References:

https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.3_.2F_4.3.1_.282017-08-10.29

Comment 4 Cedric Buissart 🐶 2017-08-11 07:36:31 UTC
Acknowledgments:

Name: the Mercurial Security Team

Comment 5 Cedric Buissart 🐶 2017-08-11 07:37:04 UTC
Created mercurial tracking bugs for this issue:

Affects: fedora-all [bug 1480454]

Comment 7 errata-xmlrpc 2017-08-17 11:07:06 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2017:2489 https://access.redhat.com/errata/RHSA-2017:2489


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