Package Instance

Improper Verification of Cryptographic Signature
libgit2 is a cross-platform, linkable library implementation of Git. When using an SSH remote with the optional libssh2 backend, libgit2 does not perform certificate checking by default. Prior versions of libgit2 require the caller to set the `certificate_check` field of libgit2's `git_remote_callbacks` structure - if a certificate check callback is not set, libgit2 does not perform any certificate checking. This means that by default - without configuring a certificate check callback, clients will not perform validation on the server SSH keys and may be subject to a man-in-the-middle attack. Users are encouraged to upgrade to v1.4.5 or v1.5.1. Users unable to upgrade should ensure that all relevant certificates are manually checked.

Out-of-bounds Read
In the library libgit2, which is used by pygit2, a remote attacker can send a crafted smart-protocol `ng` packet that lacks a `\0` byte to trigger an out-of-bounds read leading to a DoS.

Out-of-bounds Read
A flaw was found in libgit2 which is wrapped by the rugged gem. A missing check
in git_delta_apply function in `delta.c` file, may lead to an out-of-bound read while reading a binary delta file. An attacker may use this flaw to cause a Denial of Service.

Improper Input Validation
An issue was discovered in libgit2, which is used by pygit2 package: `path.c` mishandles equivalent filenames that exist because of NTFS Alternate Data Streams. This may allow remote code execution when cloning a repository.

Improper Input Validation
An issue was discovered in libgit2, which is used by pygit2 package: `checkout.c` mishandles equivalent filenames that exist because of NTFS short names.

Out-of-bounds Read
The libgit2 library, which is used by pygit2, is vulnerable to an integer overflow which leads to an out-of-bound read. An attacker may use this flaw to leak memory addresses or cause a Denial of Service.