borgbackup@1.1.0b5 vulnerabilities

Deduplicated, encrypted, authenticated and compressed backups

Direct Vulnerabilities

Known vulnerabilities in the borgbackup package. This does not include vulnerabilities belonging to this package’s dependencies.

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • M
Improper Authorization

Affected versions of this package are vulnerable to Improper Authorization due to allowing an attacker to access a mount with -o uid=1001,umask=077 as user 1000.

How to fix Improper Authorization?

Upgrade borgbackup to version 1.1.9 or higher.

[,1.1.9)
  • M
Cryptographic Operations are run Before Supporting Units are Ready

Affected versions of this package are vulnerable to Cryptographic Operations are run Before Supporting Units are Ready due to a flaw in the cryptographic authentication scheme. An attacker can fake archives and potentially indirectly cause backup data loss in the repository by inserting files (with no additional headers) into backups and gaining write access to the repository.

Note:

Data loss after being attacked can be avoided by reviewing the archives (timestamp and contents valid and as expected) after any "borg check --repair" and before "borg prune".

How to fix Cryptographic Operations are run Before Supporting Units are Ready?

Upgrade borgbackup to version 1.2.5 or higher.

[,1.2.5)
  • H
Access Restriction Bypass

borgbackup is deduplicated, encrypted, authenticated and compressed backups.

Affected versions of the package are vulnerable to Access Restriction Bypass. Incorrect implementation of access controls allows remote users to override repository restrictions in Borg servers. A user able to access a remote Borg SSH server is able to circumvent access controls post-authentication.

How to fix Access Restriction Bypass?

Upgrade borgbackup to version 1.1.3 or higher.

[1.1.0b1,1.1.3)