PatchTheCVElibgit2 project vulnerabilities
Recent CVEs affecting libgit2 project products. 5 tracked.
libgit2 project has 5 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 5. Most recent: 2017-03-24. Highest priority: CVE-2016-10128 (score 67/100).
- CVE-2016-8569 MEDIUM 5.5 UPGRADE MITIGATE The git_oid_nfmt function in commit.c in libgit2 before 0.24.3 allows remote attackers to cause a denial of se
- CVE-2016-8568 MEDIUM 5.5 MITIGATE MITIGATE The git_commit_message function in oid.c in libgit2 before 0.24.3 allows remote attackers to cause a denial of
- CVE-2016-10130 MEDIUM 5.9 UPGRADE The http_connect function in transports/http.c in libgit2 before 0.24.6 and 0.25.x before 0.25.1 might allow m
- CVE-2016-10129 HIGH 7.5 UPGRADE The Git Smart Protocol support in libgit2 before 0.24.6 and 0.25.x before 0.25.1 allows remote attackers to ca
- CVE-2016-10128 CRITICAL 9.8 UPGRADE Buffer overflow in the git_pkt_parse_line function in transports/smart_pkt.c in the Git Smart Protocol support
FAQ
How do I fix libgit2 project vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is libgit2 project being exploited right now?
None of the tracked libgit2 project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libgit2 project CVE should I patch first?
CVE-2016-10128 currently ranks highest (67/100): Buffer overflow in the git_pkt_parse_line function in transports/smart_pkt.c in the Git Smart Protocol support.