CVE-2016-10130
What it is
The http_connect function in transports/http.c in libgit2 before 0.24.6 and 0.25.x before 0.25.1 might allow man-in-the-middle attackers to spoof servers by leveraging clobbering of the error variable.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data tampering.
- Exploit odds
- 1.7% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.7% in the next 30 days (EPSS).
- Severity: 5.9 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.7% · EPSS, next 30 days
- Weakness
- CWE-284 · Improper access control
- Record status
- Modified
Affected
- libgit2 Project libgit2 ≤ 0.24.5
- libgit2 Project libgit2 0.25.0
Attack profile CVSS 3.0 · 5.9
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2016-10130.md and follow it. Check whether this project is affected by CVE-2016-10130. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://www.openwall.com/lists/oss-security/2017/01/10/5
- http://www.openwall.com/lists/oss-security/2017/01/11/6
- https://github.com/libgit2/libgit2/commit/9a64e62f0f20c9cf9b2e1609f037060eb2d8eb22
- https://github.com/libgit2/libgit2/commit/b5c6a1b407b7f8b952bded2789593b68b1876211
- https://libgit2.github.com/security/
- http://www.openwall.com/lists/oss-security/2017/01/10/5
- http://www.openwall.com/lists/oss-security/2017/01/11/6
- https://github.com/libgit2/libgit2/commit/9a64e62f0f20c9cf9b2e1609f037060eb2d8eb22
- https://github.com/libgit2/libgit2/commit/b5c6a1b407b7f8b952bded2789593b68b1876211
- https://libgit2.github.com/security/
References
- http://lists.opensuse.org/opensuse-updates/2017-02/msg00030.html
- http://lists.opensuse.org/opensuse-updates/2017-02/msg00036.html
- http://lists.opensuse.org/opensuse-updates/2017-02/msg00072.html
- http://www.openwall.com/lists/oss-security/2017/01/10/5
- http://www.openwall.com/lists/oss-security/2017/01/11/6
- http://www.securityfocus.com/bid/95359
- https://github.com/libgit2/libgit2/commit/9a64e62f0f20c9cf9b2e1609f037060eb2d8eb22
- https://github.com/libgit2/libgit2/commit/b5c6a1b407b7f8b952bded2789593b68b1876211
- https://libgit2.github.com/security/
- http://lists.opensuse.org/opensuse-updates/2017-02/msg00030.html
- http://lists.opensuse.org/opensuse-updates/2017-02/msg00036.html
- http://lists.opensuse.org/opensuse-updates/2017-02/msg00072.html
- http://www.openwall.com/lists/oss-security/2017/01/10/5
- http://www.openwall.com/lists/oss-security/2017/01/11/6
- http://www.securityfocus.com/bid/95359
- https://github.com/libgit2/libgit2/commit/9a64e62f0f20c9cf9b2e1609f037060eb2d8eb22
- https://github.com/libgit2/libgit2/commit/b5c6a1b407b7f8b952bded2789593b68b1876211
- https://libgit2.github.com/security/