A flaw was found in libgit2, an out of bounds read when parsing an "ng" packet. libgit2 keeps track of both the current position as well as the remaining length of the packet itself. But instead of taking care not to exceed the length, libgit2 passs the current pointer's position to strchr, which will search for a certain character until hitting NUL. It is thus possible to create a crafted packet which doesn't contain a NUL byte to trigger an out-of-bounds read. References: https://bugs.gentoo.org/662994 Upstream fix: https://github.com/libgit2/libgit2/commit/1f9a8510e1d2f20ed7334eeeddb92c4dd8e7c649
Created libgit2 tracking bugs for this issue: Affects: epel-all [bug 1615589] Affects: fedora-all [bug 1615587]
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2018-15501