Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1510455 - (CVE-2017-15298) CVE-2017-15298 git: Mishandling layers of tree objects
CVE-2017-15298 git: Mishandling layers of tree objects
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20171012,reported=2...
: Security
Depends On: 1510457
Blocks:
  Show dependency treegraph
 
Reported: 2017-11-07 07:55 EST by Andrej Nemec
Modified: 2018-05-10 14:23 EDT (History)
47 users (show)

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


Attachments (Terms of Use)

  None (edit)
Description Andrej Nemec 2017-11-07 07:55:30 EST
Git through 2.14.2 mishandles layers of tree objects, which allows remote attackers to cause a denial of service (memory consumption) via a crafted repository, aka a Git bomb. This can also have an impact of disk consumption; however, an affected process typically would not survive its attempt to build the data structure in memory before writing to disk.

External References:

https://kate.io/blog/git-bomb/

References:

https://github.com/Katee/git-bomb
Comment 1 Andrej Nemec 2017-11-07 07:56:48 EST
Created git tracking bugs for this issue:

Affects: fedora-all [bug 1510457]
Comment 2 Todd Zullinger 2017-11-07 11:48:34 EST
git <= 2.14.3 is vulnerable here, I believe.  The upstream commit which resolves this is https://git.kernel.org/pub/scm/git/git.git/commit/?id=a937b37e76 (merged yesterday).  I imagine we'll see some maint releases from upstream shortly.  The commit applies cleanly to 2.9.x (which f25 runs).  I didn't look any further back than that.

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