CVE-2018-10857: git-annex private data exfiltration to compromised remote

git-annex Updated 02 Oct 2025

Summary

25/07/2023
Yes i
Unrated
Not published

CVE-2018-10857: git-annex private data exfiltration to compromised remote. Affects git-annex versions < 6.20180626. Fixed in 6.20180626. How to fix ↓

Also tracked for

The same CVE-2018-10857 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

git-annex is an open-source tool that manages files with git, without checking the file contents into git. It allows users to store large files in a distributed manner while keeping track of their locations. The tool is commonly used for version control and collaboration purposes. However, certain uses of git-annex were found to be vulnerable to a private data exposure and exfiltration attack.

Vulnerability Detail

The vulnerability in git-annex allows an attacker to exfiltrate private data from a victim's repository by exploiting control over one of the remotes. The attacker can provide a malicious git-annex repository that the victim clones or gain read access to the victim's repository. By running specific commands, the attacker can trick git-annex into following URLs pointing to private data, which is then transferred to the compromised remote. This attack is most likely to succeed when the victim is running the git-annex assistant or periodically syncing content.

How To Fix

Minimum fixed version

6.20180626

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. Users are advised to update to the latest version of git-annex and configure the new security settings as necessary.

Conclusion

The vulnerability in git-annex allows an attacker to exfiltrate private data from a victim's repository by exploiting control over one of the remotes. It is crucial for users to update their git-annex installation to the latest version and configure the new security settings to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for git-annex →

Share this vulnerability

FAQ

git-annex is an open-source tool that manages files with git, allowing users to store large files in a distributed manner while keeping track of their locations.

The vulnerability allows an attacker to exfiltrate private data from a victim's repository by exploiting control over one of the remotes. By tricking git-annex into following specific URLs, the attacker can transfer the private data to a compromised remote.

The vulnerability can lead to the exposure and exfiltration of private data from a victim's git-annex repository. This can have serious consequences for the confidentiality of sensitive information.

To fix the vulnerability, users should update their git-annex installation to version 6.20180626 or later. Additionally, configuring the new security settings can further mitigate the risk.

There are no specific workarounds mentioned for this vulnerability. Updating to the latest version of git-annex is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for git-annex.

How To Fix

Minimum fixed version

6.20180626

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback