Description
pass through 1.7.3 has a possibility of using a password for an unintended resource. For exploitation to occur, the user must do a git pull, decrypt a password, and log into a remote service with the password. If an attacker controls the central Git server or one of the other members' machines, and also controls one of the services already in the password store, they can rename one of the password files in the Git repository to something else: pass doesn't correctly verify that the content of a file matches the filename, so a user might be tricked into decrypting the wrong password and sending that to a service that the attacker controls. NOTE: for environments in which this threat model is of concern, signing commits can be a solution.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | password-store | No fix yet | — |
| Debian 13 | password-store | No fix yet | — |
| Debian 12 | password-store | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | password-store | No fix yet | — |
| Ubuntu 26.04 LTS | password-store | No fix yet | — |
| Ubuntu 25.10 | password-store | No fix yet | — |
| Ubuntu 24.04 LTS | password-store | No fix yet | — |
| Ubuntu 22.04 LTS | password-store | No fix yet | — |
Show 3 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 20.04 LTS | password-store | No fix yet | — |
| Ubuntu 18.04 LTS | password-store | No fix yet | — |
| Ubuntu 16.04 LTS | password-store | No fix yet | — |