CVE-2020-12278: Critical severity centos libgcc vulnerability

Published Apr 27, 2020
·
Updated

An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. path.c mishandles equivalent filenames that exist because of NTFS Alternate Data Streams. This may allow remote code execution when cloning a repository. This issue is similar to CVE-2019-1352.

Affected Software

6 affected componentsFixes available
debian/libgit2<=0.27.7+dfsg.1-0.2
0.27.7+dfsg.1-0.2+deb10u21.1.0+dfsg.1-4+deb11u11.1.0+dfsg.1-4+deb11u21.5.1+ds-11.5.1+ds-1+deb12u11.7.2+ds-1
ubuntu/libgit2<0.26.0+dfsg.1-1.1ubuntu0.2+
0.26.0+dfsg.1-1.1ubuntu0.2+
ubuntu/libgit2<0.28.4, <0.99.0
0.28.40.99.0
ubuntu/libgit2<0.24.1-2ubuntu0.2+
0.24.1-2ubuntu0.2+
libgit2 libgit2<0.28.4
Debian Debian Linux=9.0

Remediation

Patch Available

https://github.com/libgit2/libgit2/commit/3f7851eadca36a99627ad78cbe56a40d3776ed01

Patch Available

https://github.com/libgit2/libgit2/commit/e1832eb20a7089f6383cfce474f213157f5300cb

Event History

Apr 27, 2020
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Mar 5, 2024
Data Sourced
via Launchpad·10:35 PM
Description

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2020-12278?

The severity of CVE-2020-12278 is critical, with a CVSS score of 9.8.

2

What is the affected software for CVE-2020-12278?

The affected software for CVE-2020-12278 is Libgit2 (version up to exclusive 0.28.4) and Debian Linux (version exactly 9.0).

3

How does CVE-2020-12278 occur?

CVE-2020-12278 occurs due to mishandling of equivalent filenames that exist because of NTFS Alternate Data Streams in libgit2.

4

Can CVE-2020-12278 result in remote code execution?

Yes, CVE-2020-12278 may allow remote code execution when cloning a repository.

5

How can I fix CVE-2020-12278?

To fix CVE-2020-12278, it is recommended to update to a version of libgit2 that is greater than or equal to 0.28.4 or apply the necessary patches.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203