GHSA-pxfv-7rr3-2qjg
Vulnerability from github
8.7 (High) - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Summary
All versions before 1.8.2 have a path traversal vulnerability, allowing an attacker to download unintended files from the server.
Details
Unauthenticated users were able to retrieve any files which are accessible (according to OS-level permissions) from the copyparty process. Usually, this is all files that are readable by the OS account which is used to run copyparty.
The vulnerability did not make it possible to list the contents of folders, so an attacker needs to know the full absolute path to the file, or the relative path from where copyparty is installed.
Some methods of running copyparty (prisonparty, the nix package, and docker) had a mitigating effect, mostly reducing the attack scope to files inside copyparty volumes, and possibly the copyparty config file.
Checking for attacks
Please keep in mind that, if an attacker were to find a way to overwrite the logs, for example by discovering the password to another service with sufficient privileges, then the following approaches cannot be trusted.
if copyparty was only accessible through a reverse proxy, then all attacks would be visible in the webserver access-log as URLs which contain both .cpr/ and %2F
* nginx:
bash
(gzip -dc access.log*.gz; cat access.log) | sed -r 's/" [0-9]+ .*//' | grep -E 'cpr/.*%2[^0]' | grep -vF data:image/svg
However, if copyparty was directly accessible from the internet, then any successful attacks (file retrievals) would unfortunately leave no trace. That said, it is very probable that an attacker would make at least one invalid attempt, which would become apparent in the copyparty server log, detectable with grep -aE '(Errno|Permission).*\.cpr/' revealing the following:
* python2 example: [IOError] [Errno 13] Permission denied: '/etc/shadow', .cpr//etc/shadow
* python3 example: [PermissionError] [Errno 13] Permission denied: b'/etc/shadow', .cpr//etc/shadow
Providing an exact command for this approach is difficult, as it depends on how copyparty is deployed;
* if copyparty was running as a systemd service: journalctl -am | grep -aE '(Errno|Permission).*\.cpr/'
* if copyparty was logging to a compressed file: xz -kdc thefilename.xz | grep -aE '(Errno|Permission).*\.cpr/'
* if the copyparty log is available in a plaintext file: grep -aE '(Errno|Permission).*\.cpr/' thefilename.txt
PoC / attack example
bash
curl -sik http://127.0.0.1:3923/.cpr/%2Fetc%2Fpasswd
curl -sik http://127.0.0.1:3923/.cpr/..%2F..%2F..%2F..%2F..%2Fetc%2Fpasswd
{
"affected": [
{
"ecosystem_specific": {
"affected_functions": [
"copyparty.httpcli.HttpCli.handle_get"
]
},
"package": {
"ecosystem": "PyPI",
"name": "copyparty"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.8.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2023-37474"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2023-07-14T21:59:23Z",
"nvd_published_at": "2023-07-14T20:15:09Z",
"severity": "HIGH"
},
"details": "# Summary\nAll versions before 1.8.2 have a path traversal vulnerability, allowing an attacker to download unintended files from the server.\n\n# Details\nUnauthenticated users were able to retrieve any files which are accessible (according to OS-level permissions) from the copyparty process. Usually, this is all files that are readable by the OS account which is used to run copyparty.\n\nThe vulnerability did not make it possible to list the contents of folders, so an attacker needs to know the full absolute path to the file, or the relative path from where copyparty is installed.\n\nSome methods of running copyparty ([prisonparty](https://github.com/9001/copyparty/tree/hovudstraum/bin#prisonpartysh), the [nix package](https://github.com/9001/copyparty#nix-package), and [docker](https://github.com/9001/copyparty/tree/hovudstraum/scripts/docker)) had a mitigating effect, mostly reducing the attack scope to files inside copyparty volumes, and possibly the copyparty config file.\n\n# Checking for attacks\nPlease keep in mind that, if an attacker were to find a way to overwrite the logs, for example by discovering the password to another service with sufficient privileges, then the following approaches cannot be trusted.\n\nif copyparty was only accessible through a reverse proxy, then all attacks would be visible in the webserver access-log as URLs which contain both `.cpr/` and `%2F`\n* nginx:\n ```bash\n (gzip -dc access.log*.gz; cat access.log) | sed -r \u0027s/\" [0-9]+ .*//\u0027 | grep -E \u0027cpr/.*%2[^0]\u0027 | grep -vF data:image/svg\n ```\n\nHowever, if copyparty was directly accessible from the internet, then any successful attacks (file retrievals) would unfortunately leave no trace. That said, it is very probable that an attacker would make at least one invalid attempt, which would become apparent in the copyparty server log, detectable with `grep -aE \u0027(Errno|Permission).*\\.cpr/\u0027` revealing the following:\n* python2 example: `[IOError] [Errno 13] Permission denied: \u0027/etc/shadow\u0027, .cpr//etc/shadow`\n* python3 example: `[PermissionError] [Errno 13] Permission denied: b\u0027/etc/shadow\u0027, .cpr//etc/shadow`\n \n\nProviding an exact command for this approach is difficult, as it depends on how copyparty is deployed;\n* if copyparty was running as a systemd service: `journalctl -am | grep -aE \u0027(Errno|Permission).*\\.cpr/\u0027`\n* if copyparty was logging to a compressed file: `xz -kdc thefilename.xz | grep -aE \u0027(Errno|Permission).*\\.cpr/\u0027`\n* if the copyparty log is available in a plaintext file: `grep -aE \u0027(Errno|Permission).*\\.cpr/\u0027 thefilename.txt`\n\n# PoC / attack example\n```bash\ncurl -sik http://127.0.0.1:3923/.cpr/%2Fetc%2Fpasswd\ncurl -sik http://127.0.0.1:3923/.cpr/..%2F..%2F..%2F..%2F..%2Fetc%2Fpasswd\n```\n",
"id": "GHSA-pxfv-7rr3-2qjg",
"modified": "2024-09-13T18:19:54Z",
"published": "2023-07-14T21:59:23Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/9001/copyparty/security/advisories/GHSA-pxfv-7rr3-2qjg"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-37474"
},
{
"type": "WEB",
"url": "https://github.com/9001/copyparty/commit/043e3c7dd683113e2b1c15cacb9c8e68f76513ff"
},
{
"type": "PACKAGE",
"url": "https://github.com/9001/copyparty"
},
{
"type": "WEB",
"url": "https://github.com/9001/copyparty/releases/tag/v1.8.2"
},
{
"type": "WEB",
"url": "https://github.com/pypa/advisory-database/tree/main/vulns/copyparty/PYSEC-2023-127.yaml"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/173822/Copyparty-1.8.2-Directory-Traversal.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "copyparty vulnerable to path traversal attack"
}
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.
- 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.