You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: security/index.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,10 @@ Information about security advisories affecting libgit2 and the releases that
8
8
provide resolution.
9
9
10
10
***[libgit2 v0.24.6](https://github.com/libgit2/libgit2/releases/tag/v0.24.6)** and **[libgit2 v0.25.1](https://github.com/libgit2/libgit2/releases/tag/v0.25.1)**, January 9th, 2017
11
-
Includes two fixes, one performs extra sanitization for some edge cases in the Git Smart Prot
12
-
ocol which can lead to attempting to parse outside of the buffer.<br>
13
-
The second fix affects the certificate check callback. It provides a `valid` parameter to indicate whether the native cryptographic library considered the certificate to be correct. This parameter is always `1`/`true` before these releases leading to a possible MITM.<br>
11
+
Includes two fixes, one performs extra sanitization for some edge cases in the Git Smart Protocol which can lead to attempting to parse outside of the buffer.
12
+
13
+
The second fix affects the certificate check callback. It provides a `valid` parameter to indicate whether the native cryptographic library considered the certificate to be correct. This parameter is always `1`/`true` before these releases leading to a possible MITM.
14
+
14
15
This does not affect you if you do not use the custom certificate callback or if you do not take this value into account. This does affect you if you use pygit2 or git2go regardless of whether you specify a certificate check callback.
15
16
16
17
***[libgit2 v0.22.1](https://github.com/libgit2/libgit2/releases/tag/v0.22.1)**, January 16, 2015
0 commit comments