1.4.0
9 years ago
5 months ago
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 freeVulnerability | Vulnerable Version |
---|---|
Affected versions of this package are vulnerable to Improper Authorization due to allowing an attacker to access a mount with How to fix Improper Authorization? Upgrade | [,1.1.9) |
Affected versions of this package are vulnerable to Improper Input Validation leading to insecure path manipulation. When using e.g. How to fix Improper Input Validation? Upgrade | [,1.0.7) |
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 | [,1.2.5) |
Affected versions of this package are vulnerable to Authentication Bypass by Spoofing the list of Archives. Borg (aka BorgBackup) before 1.0.9 has a flaw in the cryptographic protocol used to authenticate the manifest (list of archives), potentially allowing an attacker to spoof the list of archives. | [,1.0.9) |
Affected versions of this package are vulnerable to Arbitrary File Overwrite. BorgBackup before 1.0.9 has a flaw in the way duplicate archive names were processed during manifest recovery, potentially allowing an attacker to overwrite an archive. | [,1.0.9) |