pysec-2023-164
Vulnerability from pysec
borgbackup is an opensource, deduplicating archiver with compression and authenticated encryption. A flaw in the cryptographic authentication scheme in borgbackup allowed an attacker to fake archives and potentially indirectly cause backup data loss in the repository. The attack requires an attacker to be able to: 1. insert files (with no additional headers) into backups and 2. gain write access to the repository. This vulnerability does not disclose plaintext to the attacker, nor does it affect the authenticity of existing archives. Creating plausible fake archives may be feasible for empty or small archives, but is unlikely for large archives. The issue has been fixed in borgbackup 1.2.5. Users are advised to upgrade. Additionally to installing the fixed code, users must follow the upgrade procedure as documented in the change log. 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". There are no known workarounds for this vulnerability.
| Name | purl | borgbackup | pkg:pypi/borgbackup |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "borgbackup",
"purl": "pkg:pypi/borgbackup"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3eb070191da10c2d3f7bc6484cf3d51c3045f884"
}
],
"repo": "https://github.com/borgbackup/borg",
"type": "GIT"
},
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.2.5"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.23.0",
"0.24.0",
"0.25.0",
"0.26.0",
"0.26.1",
"0.27.0",
"0.28.0",
"0.28.1",
"0.28.2",
"0.29.0",
"0.30.0",
"0.30.1",
"1.0.0",
"1.0.0rc1",
"1.0.0rc2",
"1.0.1",
"1.0.10",
"1.0.10rc1",
"1.0.11",
"1.0.11rc1",
"1.0.12",
"1.0.13",
"1.0.2",
"1.0.3",
"1.0.4",
"1.0.5",
"1.0.6",
"1.0.6rc1",
"1.0.7",
"1.0.7rc1",
"1.0.7rc2",
"1.0.8",
"1.0.8rc1",
"1.0.9",
"1.0.9rc1",
"1.1.0",
"1.1.0b1",
"1.1.0b2",
"1.1.0b3",
"1.1.0b4",
"1.1.0b5",
"1.1.0b6",
"1.1.0rc1",
"1.1.0rc2",
"1.1.0rc3",
"1.1.0rc4",
"1.1.1",
"1.1.10",
"1.1.11",
"1.1.12",
"1.1.13",
"1.1.14",
"1.1.15",
"1.1.16",
"1.1.17",
"1.1.18",
"1.1.2",
"1.1.3",
"1.1.4",
"1.1.5",
"1.1.6",
"1.1.7",
"1.1.8",
"1.1.9",
"1.2.0",
"1.2.0a2",
"1.2.0a3",
"1.2.0a4",
"1.2.0a5",
"1.2.0a6",
"1.2.0a7",
"1.2.0a8",
"1.2.0a9",
"1.2.0b1",
"1.2.0b2",
"1.2.0b3",
"1.2.0b4",
"1.2.0rc1",
"1.2.1",
"1.2.2",
"1.2.3",
"1.2.4"
]
}
],
"aliases": [
"CVE-2023-36811",
"GHSA-8fjr-hghr-4m99"
],
"details": "borgbackup is an opensource, deduplicating archiver with compression and authenticated encryption. A flaw in the cryptographic authentication scheme in borgbackup allowed an attacker to fake archives and potentially indirectly cause backup data loss in the repository. The attack requires an attacker to be able to: 1. insert files (with no additional headers) into backups and 2. gain write access to the repository. This vulnerability does not disclose plaintext to the attacker, nor does it affect the authenticity of existing archives. Creating plausible fake archives may be feasible for empty or small archives, but is unlikely for large archives. The issue has been fixed in borgbackup 1.2.5. Users are advised to upgrade. Additionally to installing the fixed code, users must follow the upgrade procedure as documented in the change log. 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\". There are no known workarounds for this vulnerability.",
"id": "PYSEC-2023-164",
"modified": "2023-09-06T16:31:20.448538+00:00",
"published": "2023-08-30T18:15:00+00:00",
"references": [
{
"type": "WEB",
"url": "https://github.com/borgbackup/borg/blob/1.2.5-cvedocs/docs/changes.rst#pre-125-archives-spoofing-vulnerability-cve-2023-36811"
},
{
"type": "FIX",
"url": "https://github.com/borgbackup/borg/commit/3eb070191da10c2d3f7bc6484cf3d51c3045f884"
},
{
"type": "ADVISORY",
"url": "https://github.com/borgbackup/borg/security/advisories/GHSA-8fjr-hghr-4m99"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.