Archive spoofing via unchecked TAM authentication
Published Aug 30, 2023 · Updated Feb 13, 2025
Improper cryptographic verification in Borg before 1.2.5 allows local users with repository write access to spoof backup archives. Archive loading and repair paths unpack archive metadata without requiring or validating its TAM authentication tag. Exploitation requires both insertion of headerless files into a backup and write access to its repository; forged archives can trigger indirect backup-data loss, but cannot expose plaintext or invalidate existing archives.
Summary
What happened
Improper cryptographic verification in Borg before 1.2.5 allows local users with repository write access to spoof backup archives. Archive loading and repair paths unpack archive metadata without requiring or validating its TAM authentication tag. Exploitation requires both insertion of headerless files into a backup and write access to its repository; forged archives can trigger indirect backup-data loss, but cannot expose plaintext or invalidate existing archives.
The record
- CVE
- CVE-2023-36811
- Published
- Aug 30, 2023
- Updated
- Feb 13, 2025
- Vendor
- BorgBackup
- Product
- Borg
- Classifications
- CWE-347, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 30, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.2.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo