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 doesnt 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.
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Password-store | Zx2c4 | * | 1.7.3 (including) |
| Password-store | Ubuntu | bionic | * |
| Password-store | Ubuntu | groovy | * |
| Password-store | Ubuntu | hirsute | * |
| Password-store | Ubuntu | impish | * |
| Password-store | Ubuntu | kinetic | * |
| Password-store | Ubuntu | lunar | * |
| Password-store | Ubuntu | mantic | * |
| Password-store | Ubuntu | trusty | * |
| Password-store | Ubuntu | xenial | * |