Bug 1429936 - subversion: SHA-1 collision causes repository breakage
Summary: subversion: SHA-1 collision causes repository breakage
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1429939
Blocks: 1429938
TreeView+ depends on / blocked
Reported: 2017-03-07 14:29 UTC by Andrej Nemec
Modified: 2021-02-17 02:29 UTC (History)
3 users (show)

Fixed In Version: subversion 1.8.18, subversion 1.9.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-08 03:08:47 UTC

Attachments (Terms of Use)

Comment 1 Andrej Nemec 2017-03-07 14:31:30 UTC
Created subversion tracking bugs for this issue:

Affects: fedora-all [bug 1429939]

Comment 3 Doran Moppert 2017-04-03 05:19:09 UTC

If you have a Subversion repository which accepts commits from untrusted users, installing the following script as a commit hook will reject files which correspond to known SHA-1 collisions.


Further measures to protect the repository or recover from a malicious commit are described in this mailing list post:


Comment 4 Doran Moppert 2017-04-04 06:36:28 UTC
subversion-1.6 is not impacted as badly by this issue because it does not include the `enable-rep-sharing` feature.  If two colliding files are committed, they can both be checked out correctly.  On subversion-1.7 this is not the case unless `enable-rep-sharing` has been set to `false` in the repository configuration.

This issue does not appear to cause any irrecoverable damage to the affected repository.  Downstream components such as trac can be adversely affected until one of the colliding files is removed.

Comment 5 Doran Moppert 2017-04-04 06:40:39 UTC

Red Hat Product Security has rated this issue as having Moderate 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/.

Comment 6 Adam Mariš 2017-07-04 08:19:33 UTC
External References:


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