Affected: Homebrew: git-annex

# *git-annex* private data exfiltration to compromised remote

Some uses of git-annex were vulnerable to a private data exposure and exfiltration attack. It could expose the content of files located outside the *git-annex* repository, or content from a private web server on localhost or the LAN. Joey Hess discovered this attack.

To perform this attack, the attacker needs to have control over one of the remotes of the victim's *git-annex* repository. For example, they may provide a public *git-annex* repository that the victim clones. Or, equivalantly, the attacker could have read access to the victim's *git-annex* repository or a repository it pushes to, and some channel to get commits into it (e.g. pull requests).

These exploits are most likely to succeed when the victim is running the `git-annex` assistant, or is periodically running `git annex sync --content`.

To perform the attack the attacker runs `git-annex addurl --relaxed file:///etc/passwd` and commits this to the repository in some out of the way place. After the victim's git repository receives that change, `git-annex` follows the attacker-provided URL to the private data, which it stores in the *git-annex* repository. From there it transfers the content to the remote *git-annex* repository that the attacker has access to.

As well as `file:///` URLs, the attacker can use URLs to private web servers. The URL can also be one that the attacker controls, that redirects to a URL that is accessible to the victim…

git-annex is vulnerable to a private data exposure and exfiltration attack. It could expose the content of files located outside the git-annex repository, or content from a private web server on localhost or the LAN.

git-annex is vulnerable to a private data exposure and exfiltration attack. It could expose the content of files located outside the git-annex repository, or content from a private web server on localhost or the LAN.

Affected: Hackage: git-annex

# *git-annex* private data exfiltration to compromised remote

Some uses of git-annex were vulnerable to a private data exposure and exfiltration attack. It could expose the content of files located outside the *git-annex* repository, or content from a private web server on localhost or the LAN. Joey Hess discovered this attack.

To perform this attack, the attacker needs to have control over one of the remotes of the victim's *git-annex* repository. For example, they may provide a public *git-annex* repository that the victim clones. Or, equivalantly, the attacker could have read access to the victim's *git-annex* repository or a repository it pushes to, and some channel to get commits into it (e.g. pull requests).

These exploits are most likely to succeed when the victim is running the `git-annex` assistant, or is periodically running `git annex sync --content`.

To perform the attack the attacker runs `git-annex addurl --relaxed file:///etc/passwd` and commits this to the repository in some out of the way place. After the victim's git repository receives that change, `git-annex` follows the attacker-provided URL to the private data, which it stores in the *git-annex* repository. From there it transfers the content to the remote *git-annex* repository that the attacker has access to.

As well as `file:///` URLs, the attacker can use URLs to private web servers. The URL can also be one that the attacker controls, that redirects to a URL that is accessible to the victim…

Affected: Ubuntu:16.04:LTS: git-annex, Ubuntu:18.04:LTS: git-annex

git-annex is vulnerable to a private data exposure and exfiltration attack. It could expose the content of files located outside the git-annex repository, or content from a private web server on localhost or the LAN.