CWE-22
Allowed-with-ReviewImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Abstraction: Base · Status: Stable
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
13302 vulnerabilities reference this CWE, most recent first.
GHSA-M63Q-4HR8-5R5H
Vulnerability from github – Published: 2025-06-13 15:30 – Updated: 2025-06-13 22:17Directory Traversal vulnerability in solon v.3.1.2 allows a remote attacker to conduct XSS attacks via the solon-faas-luffy component
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "org.noear:solon-faas-luffy"
},
"ranges": [
{
"events": [
{
"introduced": "3.1.2"
},
{
"fixed": "3.2.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-46096"
],
"database_specific": {
"cwe_ids": [
"CWE-22",
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2025-06-13T22:17:44Z",
"nvd_published_at": "2025-06-13T13:15:21Z",
"severity": "MODERATE"
},
"details": "Directory Traversal vulnerability in solon v.3.1.2 allows a remote attacker to conduct XSS attacks via the solon-faas-luffy component",
"id": "GHSA-m63q-4hr8-5r5h",
"modified": "2025-06-13T22:17:44Z",
"published": "2025-06-13T15:30:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-46096"
},
{
"type": "WEB",
"url": "https://github.com/opensolon/solon/issues/357"
},
{
"type": "WEB",
"url": "https://github.com/opensolon/solon/commit/49a3bf95fdcf050829843004b65a2b336ca6ddff"
},
{
"type": "WEB",
"url": "https://gist.github.com/yaoyao-cool/1b7d80930fea88b6fd4839646cedc437"
},
{
"type": "PACKAGE",
"url": "https://github.com/opensolon/solon"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Solon Vulnerable to Directory Traversal"
}
GHSA-M63R-M9JH-3VC6
Vulnerability from github – Published: 2026-04-14 23:23 – Updated: 2026-04-24 20:41Summary
The directory traversal fix introduced in commit 2375eb5e0 for objects/aVideoEncoderReceiveImage.json.php only checks the URL path component (via parse_url($url, PHP_URL_PATH)) for .. sequences. However, the downstream function try_get_contents_from_local() in objects/functionsFile.php uses explode('/videos/', $url) on the full URL string including the query string. An attacker can place the /videos/../../ traversal payload in the query string to bypass the security check and read arbitrary files from the server filesystem.
Details
The security fix at commit 2375eb5e0 added a traversal check at objects/aVideoEncoderReceiveImage.json.php:49:
$decodedPath = urldecode((string)(parse_url($_REQUEST[$value], PHP_URL_PATH) ?? ''));
if (strpos($decodedPath, '..') !== false) {
unset($_REQUEST[$value]);
}
This only inspects the path component of the URL. For a URL like http://TARGET/x?a=/videos/../../etc/passwd, parse_url() returns /x as the path — no .. is found.
The URL then passes through isValidURL() (objects/functions.php:4203) which accepts it because FILTER_VALIDATE_URL considers .. in query strings valid per RFC 3986.
It also passes isSSRFSafeURL() (objects/functions.php:4264) because the host matches webSiteRootURL, causing an early return at line 4294.
The URL reaches url_get_contents() (objects/functions.php:1938) which calls try_get_contents_from_local() (objects/functionsFile.php:214):
function try_get_contents_from_local($url)
{
// ...
$parts = explode('/videos/', $url);
if (!empty($parts[1])) {
// ...
$tryFile = "{$global['systemRootPath']}{$encoder}videos/{$parts[1]}";
if (file_exists($tryFile)) {
return file_get_contents($tryFile);
}
}
return false;
}
explode('/videos/', $url) operates on the entire URL string including the query string. For the malicious URL, $parts[1] becomes ../../../../../../etc/passwd, constructing a path like /var/www/html/AVideo/Encoder/videos/../../../../../../etc/passwd which PHP's filesystem functions resolve to /etc/passwd.
The file content is returned to the caller and written to the video's thumbnail path via _file_put_contents(). All four downloadURL_* parameters (downloadURL_image, downloadURL_gifimage, downloadURL_webpimage, downloadURL_spectrumimage) are affected.
PoC
Prerequisites: An authenticated AVideo user account with upload permission and an existing video they own (with known videos_id).
-
Identify the AVideo instance's domain (e.g.,
https://avideo.example.com). -
Send a POST request to the ReceiveImage endpoint with the traversal payload in the query string:
curl -s -b "PHPSESSID=<session_cookie>" \
"https://avideo.example.com/objects/aVideoEncoderReceiveImage.json.php" \
-d "videos_id=<YOUR_VIDEO_ID>" \
-d "downloadURL_image=http://avideo.example.com/x?a=/videos/../../../../../../etc/passwd"
-
The response will include
jpgDestSizeindicating the file was read and written (confirming file existence and revealing file size). -
For files that pass image validation (e.g., other users' uploaded images at known paths), the content persists at the video's thumbnail URL and can be retrieved:
curl -s "https://avideo.example.com/videos/<videoFileName>.jpg"
- Non-image files (e.g.,
/etc/passwd, configuration files) are written but then deleted bydeleteInvalidImage(). However, file existence and size are still leaked, and a race condition exists between the write and the deletion.
Impact
- Arbitrary file read: An authenticated user with upload permission can read any file on the server filesystem that the web server process has access to. Files that pass image validation (PNG/JPEG/GIF) are fully exfiltrable via the video thumbnail URL.
- Information disclosure: For non-image files, file existence and size are leaked through the
jpgDestSizeresponse field. - Configuration exposure: Server configuration files, database credentials (
videos/configuration.php), and other sensitive data can be targeted. While PHP files would be deleted bydeleteInvalidImage, there is a race window between write and deletion. - Bypass of security fix: This directly bypasses the path traversal mitigation added in commit 2375eb5e0.
Recommended Fix
The .. check in aVideoEncoderReceiveImage.json.php should inspect the full URL (after URL-decoding), not just the path component. Additionally, try_get_contents_from_local() should validate its derived path.
Fix 1 — Check the full URL in ReceiveImage (objects/aVideoEncoderReceiveImage.json.php:49):
// Replace:
$decodedPath = urldecode((string)(parse_url($_REQUEST[$value], PHP_URL_PATH) ?? ''));
if (strpos($decodedPath, '..') !== false) {
// With:
$decodedFull = urldecode((string)$_REQUEST[$value]);
if (strpos($decodedFull, '..') !== false) {
Fix 2 — Add path validation in try_get_contents_from_local (objects/functionsFile.php:229):
$tryFile = "{$global['systemRootPath']}{$encoder}videos/{$parts[1]}";
// Add traversal check:
$realTryFile = realpath($tryFile);
$videosDir = realpath("{$global['systemRootPath']}{$encoder}videos/");
if ($realTryFile === false || !str_starts_with($realTryFile, $videosDir)) {
return false;
}
if (file_exists($tryFile)) {
return file_get_contents($tryFile);
}
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "wwbn/avideo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "29.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-41062"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-14T23:23:14Z",
"nvd_published_at": "2026-04-21T23:16:21Z",
"severity": "MODERATE"
},
"details": "## Summary\n\nThe directory traversal fix introduced in commit 2375eb5e0 for `objects/aVideoEncoderReceiveImage.json.php` only checks the URL **path component** (via `parse_url($url, PHP_URL_PATH)`) for `..` sequences. However, the downstream function `try_get_contents_from_local()` in `objects/functionsFile.php` uses `explode(\u0027/videos/\u0027, $url)` on the **full URL string** including the query string. An attacker can place the `/videos/../../` traversal payload in the query string to bypass the security check and read arbitrary files from the server filesystem.\n\n## Details\n\nThe security fix at commit 2375eb5e0 added a traversal check at `objects/aVideoEncoderReceiveImage.json.php:49`:\n\n```php\n$decodedPath = urldecode((string)(parse_url($_REQUEST[$value], PHP_URL_PATH) ?? \u0027\u0027));\nif (strpos($decodedPath, \u0027..\u0027) !== false) {\n unset($_REQUEST[$value]);\n}\n```\n\nThis only inspects the **path component** of the URL. For a URL like `http://TARGET/x?a=/videos/../../etc/passwd`, `parse_url()` returns `/x` as the path \u2014 no `..` is found.\n\nThe URL then passes through `isValidURL()` (`objects/functions.php:4203`) which accepts it because `FILTER_VALIDATE_URL` considers `..` in query strings valid per RFC 3986.\n\nIt also passes `isSSRFSafeURL()` (`objects/functions.php:4264`) because the host matches `webSiteRootURL`, causing an early return at line 4294.\n\nThe URL reaches `url_get_contents()` (`objects/functions.php:1938`) which calls `try_get_contents_from_local()` (`objects/functionsFile.php:214`):\n\n```php\nfunction try_get_contents_from_local($url)\n{\n // ...\n $parts = explode(\u0027/videos/\u0027, $url);\n if (!empty($parts[1])) {\n // ...\n $tryFile = \"{$global[\u0027systemRootPath\u0027]}{$encoder}videos/{$parts[1]}\";\n if (file_exists($tryFile)) {\n return file_get_contents($tryFile);\n }\n }\n return false;\n}\n```\n\n`explode(\u0027/videos/\u0027, $url)` operates on the **entire URL string** including the query string. For the malicious URL, `$parts[1]` becomes `../../../../../../etc/passwd`, constructing a path like `/var/www/html/AVideo/Encoder/videos/../../../../../../etc/passwd` which PHP\u0027s filesystem functions resolve to `/etc/passwd`.\n\nThe file content is returned to the caller and written to the video\u0027s thumbnail path via `_file_put_contents()`. All four `downloadURL_*` parameters (`downloadURL_image`, `downloadURL_gifimage`, `downloadURL_webpimage`, `downloadURL_spectrumimage`) are affected.\n\n## PoC\n\nPrerequisites: An authenticated AVideo user account with upload permission and an existing video they own (with known `videos_id`).\n\n1. Identify the AVideo instance\u0027s domain (e.g., `https://avideo.example.com`).\n\n2. Send a POST request to the ReceiveImage endpoint with the traversal payload in the query string:\n\n```bash\ncurl -s -b \"PHPSESSID=\u003csession_cookie\u003e\" \\\n \"https://avideo.example.com/objects/aVideoEncoderReceiveImage.json.php\" \\\n -d \"videos_id=\u003cYOUR_VIDEO_ID\u003e\" \\\n -d \"downloadURL_image=http://avideo.example.com/x?a=/videos/../../../../../../etc/passwd\"\n```\n\n3. The response will include `jpgDestSize` indicating the file was read and written (confirming file existence and revealing file size).\n\n4. For files that pass image validation (e.g., other users\u0027 uploaded images at known paths), the content persists at the video\u0027s thumbnail URL and can be retrieved:\n\n```bash\ncurl -s \"https://avideo.example.com/videos/\u003cvideoFileName\u003e.jpg\"\n```\n\n5. Non-image files (e.g., `/etc/passwd`, configuration files) are written but then deleted by `deleteInvalidImage()`. However, file existence and size are still leaked, and a race condition exists between the write and the deletion.\n\n## Impact\n\n- **Arbitrary file read**: An authenticated user with upload permission can read any file on the server filesystem that the web server process has access to. Files that pass image validation (PNG/JPEG/GIF) are fully exfiltrable via the video thumbnail URL.\n- **Information disclosure**: For non-image files, file existence and size are leaked through the `jpgDestSize` response field.\n- **Configuration exposure**: Server configuration files, database credentials (`videos/configuration.php`), and other sensitive data can be targeted. While PHP files would be deleted by `deleteInvalidImage`, there is a race window between write and deletion.\n- **Bypass of security fix**: This directly bypasses the path traversal mitigation added in commit 2375eb5e0.\n\n## Recommended Fix\n\nThe `..` check in `aVideoEncoderReceiveImage.json.php` should inspect the **full URL** (after URL-decoding), not just the path component. Additionally, `try_get_contents_from_local()` should validate its derived path.\n\n**Fix 1 \u2014 Check the full URL in ReceiveImage (objects/aVideoEncoderReceiveImage.json.php:49):**\n\n```php\n// Replace:\n$decodedPath = urldecode((string)(parse_url($_REQUEST[$value], PHP_URL_PATH) ?? \u0027\u0027));\nif (strpos($decodedPath, \u0027..\u0027) !== false) {\n\n// With:\n$decodedFull = urldecode((string)$_REQUEST[$value]);\nif (strpos($decodedFull, \u0027..\u0027) !== false) {\n```\n\n**Fix 2 \u2014 Add path validation in try_get_contents_from_local (objects/functionsFile.php:229):**\n\n```php\n$tryFile = \"{$global[\u0027systemRootPath\u0027]}{$encoder}videos/{$parts[1]}\";\n// Add traversal check:\n$realTryFile = realpath($tryFile);\n$videosDir = realpath(\"{$global[\u0027systemRootPath\u0027]}{$encoder}videos/\");\nif ($realTryFile === false || !str_starts_with($realTryFile, $videosDir)) {\n return false;\n}\nif (file_exists($tryFile)) {\n return file_get_contents($tryFile);\n}\n```",
"id": "GHSA-m63r-m9jh-3vc6",
"modified": "2026-04-24T20:41:10Z",
"published": "2026-04-14T23:23:14Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-f4f9-627c-jh33"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-m63r-m9jh-3vc6"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-41062"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/commit/2375eb5e0a6d3cbcfb05377657d0820a7d470b1d"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/commit/bd11c16ec894698e54e2cdae25026c61ad1ed441"
},
{
"type": "PACKAGE",
"url": "https://github.com/WWBN/AVideo"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "WWBN AVideo has an Incomplete fix: Directory traversal bypass via query string in ReceiveImage downloadURL parameters"
}
GHSA-M63V-P8HP-RG28
Vulnerability from github – Published: 2023-10-15 21:30 – Updated: 2024-04-04 08:38A directory traversal vulnerability in Valve Counter-Strike 8684 allows a client (with remote control access to a game server) to read arbitrary files from the underlying server via the motdfile console variable.
{
"affected": [],
"aliases": [
"CVE-2023-38312"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-10-15T19:15:09Z",
"severity": "HIGH"
},
"details": "A directory traversal vulnerability in Valve Counter-Strike 8684 allows a client (with remote control access to a game server) to read arbitrary files from the underlying server via the motdfile console variable.",
"id": "GHSA-m63v-p8hp-rg28",
"modified": "2024-04-04T08:38:52Z",
"published": "2023-10-15T21:30:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-38312"
},
{
"type": "WEB",
"url": "https://github.com/MikeIsAStar/Counter-Strike-Arbitrary-File-Read"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-M658-JV2R-HM53
Vulnerability from github – Published: 2026-07-18 09:32 – Updated: 2026-07-18 09:32VMware Avi Load Balancer contains a directory traversal vulnerability. Flaws in file path validation allow malicious, authenticated network users to perform directory traversal attacks.
Affected versions: 32.1.1 (fixed in 32.1.2) 31.1.1 through 31.2.2 (fixed in 31.2.2-2p3) 30.1.1 through 30.2.6 (fixed in 30.2.7) 22.1.1 through 22.1.7 (fixed in 30.2.7)
{
"affected": [],
"aliases": [
"CVE-2026-47871"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-18T09:17:08Z",
"severity": "HIGH"
},
"details": "VMware Avi Load Balancer contains a directory traversal vulnerability. Flaws in file path validation allow malicious, authenticated network users to perform directory traversal attacks.\n\nAffected versions:\n32.1.1 (fixed in 32.1.2)\n31.1.1 through 31.2.2 (fixed in 31.2.2-2p3)\n30.1.1 through 30.2.6 (fixed in 30.2.7)\n22.1.1 through 22.1.7 (fixed in 30.2.7)",
"id": "GHSA-m658-jv2r-hm53",
"modified": "2026-07-18T09:32:18Z",
"published": "2026-07-18T09:32:18Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-47871"
},
{
"type": "WEB",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/37926"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-M65C-W77G-M7JV
Vulnerability from github – Published: 2024-05-03 18:30 – Updated: 2024-11-25 18:33Directory Traversal vulnerability in codesiddhant Jasmin Ransomware v.1.0.1 allows an attacker to obtain sensitive information via the download_file.php component.
{
"affected": [],
"aliases": [
"CVE-2024-30851"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-05-03T17:15:07Z",
"severity": "MODERATE"
},
"details": "Directory Traversal vulnerability in codesiddhant Jasmin Ransomware v.1.0.1 allows an attacker to obtain sensitive information via the download_file.php component.",
"id": "GHSA-m65c-w77g-m7jv",
"modified": "2024-11-25T18:33:24Z",
"published": "2024-05-03T18:30:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-30851"
},
{
"type": "WEB",
"url": "https://github.com/chebuya/CVE-2024-30851-jasmin-ransomware-path-traversal-poc"
},
{
"type": "WEB",
"url": "https://github.com/codesiddhant/Jasmin-Ransomware"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-M65H-2C6X-9769
Vulnerability from github – Published: 2022-05-24 19:03 – Updated: 2022-05-24 19:03Improper limitation of a pathname to a restricted directory ('Path Traversal') vulnerability container volume management component in Synology Docker before 18.09.0-0515 allows local users to read or write arbitrary files via unspecified vectors.
{
"affected": [],
"aliases": [
"CVE-2021-33183"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-06-01T14:15:00Z",
"severity": "HIGH"
},
"details": "Improper limitation of a pathname to a restricted directory (\u0027Path Traversal\u0027) vulnerability container volume management component in Synology Docker before 18.09.0-0515 allows local users to read or write arbitrary files via unspecified vectors.",
"id": "GHSA-m65h-2c6x-9769",
"modified": "2022-05-24T19:03:43Z",
"published": "2022-05-24T19:03:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-33183"
},
{
"type": "WEB",
"url": "https://www.synology.com/security/advisory/Synology_SA_21_08"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-M65R-XXVX-W597
Vulnerability from github – Published: 2022-05-14 03:48 – Updated: 2022-05-14 03:48An issue was discovered in Skybox Platform before 7.5.201. Directory Traversal exists in /skyboxview/webskybox/attachmentdownload and /skyboxview/webskybox/filedownload via the tempFileName parameter.
{
"affected": [],
"aliases": [
"CVE-2015-9250"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-01-12T22:29:00Z",
"severity": "HIGH"
},
"details": "An issue was discovered in Skybox Platform before 7.5.201. Directory Traversal exists in /skyboxview/webskybox/attachmentdownload and /skyboxview/webskybox/filedownload via the tempFileName parameter.",
"id": "GHSA-m65r-xxvx-w597",
"modified": "2022-05-14T03:48:39Z",
"published": "2022-05-14T03:48:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-9250"
},
{
"type": "WEB",
"url": "https://www.sec-consult.com/fxdata/seccons/prod/temedia/advisories_txt/20151210-0_Skybox_Platform_Multiple_Vulnerabilities_v10.txt"
}
],
"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"
}
]
}
GHSA-M665-JG8V-5M5R
Vulnerability from github – Published: 2022-04-20 00:00 – Updated: 2022-04-28 00:00The Simple File List WordPress plugin is vulnerable to Arbitrary File Download via the eeFile parameter found in the ~/includes/ee-downloader.php file due to missing controls which makes it possible unauthenticated attackers to supply a path to a file that will subsequently be downloaded, in versions up to and including 3.2.7.
{
"affected": [],
"aliases": [
"CVE-2022-1119"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-04-19T21:15:00Z",
"severity": "HIGH"
},
"details": "The Simple File List WordPress plugin is vulnerable to Arbitrary File Download via the eeFile parameter found in the ~/includes/ee-downloader.php file due to missing controls which makes it possible unauthenticated attackers to supply a path to a file that will subsequently be downloaded, in versions up to and including 3.2.7.",
"id": "GHSA-m665-jg8v-5m5r",
"modified": "2022-04-28T00:00:40Z",
"published": "2022-04-20T00:00:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-1119"
},
{
"type": "WEB",
"url": "https://docs.google.com/document/d/1qIZXTzEpI4tO6832vk1KfsSAroT0FY2l--THlhJ8z3c/edit"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/simple-file-list/trunk/includes/ee-downloader.php?rev=2071880"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/075a3cc5-1970-4b64-a16f-3ec97e22b606"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/ff21241d-e488-4460-b8c2-d5a070c8c107?source=cve"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/vulnerability-advisories/#CVE-2022-1119"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-M66H-R9W4-MJ7G
Vulnerability from github – Published: 2023-06-29 00:31 – Updated: 2024-04-04 05:16Traggo Server 0.3.0 is vulnerable to directory traversal via a crafted GET request.
{
"affected": [],
"aliases": [
"CVE-2023-34843"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-06-29T00:15:09Z",
"severity": "HIGH"
},
"details": "Traggo Server 0.3.0 is vulnerable to directory traversal via a crafted GET request.",
"id": "GHSA-m66h-r9w4-mj7g",
"modified": "2024-04-04T05:16:43Z",
"published": "2023-06-29T00:31:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-34843"
},
{
"type": "WEB",
"url": "https://github.com/rootd4ddy/CVE-2023-34843"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-M66R-9QPP-V37J
Vulnerability from github – Published: 2022-05-24 19:18 – Updated: 2022-05-24 19:18As a result of an unquoted service path vulnerability present in the Kiwi CatTools Installation Wizard, a local attacker could gain escalated privileges by inserting an executable into the path of the affected service or uninstall entry.
{
"affected": [],
"aliases": [
"CVE-2021-35230"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-10-22T12:15:00Z",
"severity": "HIGH"
},
"details": "As a result of an unquoted service path vulnerability present in the Kiwi CatTools Installation Wizard, a local attacker could gain escalated privileges by inserting an executable into the path of the affected service or uninstall entry.",
"id": "GHSA-m66r-9qpp-v37j",
"modified": "2022-05-24T19:18:41Z",
"published": "2022-05-24T19:18:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-35230"
},
{
"type": "WEB",
"url": "https://www.solarwinds.com/trust-center/security-advisories/cve-2021-35230"
}
],
"schema_version": "1.4.0",
"severity": []
}
Mitigation MIT-5.1
Strategy: Input Validation
- Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.
- Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.
Mitigation MIT-15
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Mitigation MIT-20.1
Strategy: Input Validation
- Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
- Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links (CWE-23, CWE-59). This includes:
- realpath() in C
- getCanonicalPath() in Java
- GetFullPath() in ASP.NET
- realpath() or abs_path() in Perl
- realpath() in PHP
Mitigation MIT-4
Strategy: Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
Mitigation MIT-29
Strategy: Firewall
Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
Mitigation MIT-17
Strategy: Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
Mitigation MIT-21.1
Strategy: Enforcement by Conversion
- When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
- For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap [REF-185] provide this capability.
Mitigation MIT-22
Strategy: Sandbox or Jail
- Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
- OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
- This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
- Be careful to avoid CWE-243 and other weaknesses related to jails.
Mitigation MIT-34
Strategy: Attack Surface Reduction
- Store library, include, and utility files outside of the web document root, if possible. Otherwise, store them in a separate directory and use the web server's access control capabilities to prevent attackers from directly requesting them. One common practice is to define a fixed constant in each calling program, then check for the existence of the constant in the library/include file; if the constant does not exist, then the file was directly requested, and it can exit immediately.
- This significantly reduces the chance of an attacker being able to bypass any protection mechanisms that are in the base program but not in the include files. It will also reduce the attack surface.
Mitigation MIT-39
- Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
- If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
- Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
- In the context of path traversal, error messages which disclose path information can help attackers craft the appropriate attack strings to move through the file system hierarchy.
Mitigation MIT-16
Strategy: Environment Hardening
When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.
CAPEC-126: Path Traversal
An adversary uses path manipulation methods to exploit insufficient input validation of a target to obtain access to data that should be not be retrievable by ordinary well-formed requests. A typical variety of this attack involves specifying a path to a desired file together with dot-dot-slash characters, resulting in the file access API or function traversing out of the intended directory structure and into the root file system. By replacing or modifying the expected path information the access function or API retrieves the file desired by the attacker. These attacks either involve the attacker providing a complete path to a targeted file or using control characters (e.g. path separators (/ or \) and/or dots (.)) to reach desired directories or files.
CAPEC-64: Using Slashes and URL Encoding Combined to Bypass Validation Logic
This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.
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.
CAPEC-78: Using Escaped Slashes in Alternate Encoding
This attack targets the use of the backslash in alternate encoding. An adversary can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the adversary tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.
CAPEC-79: Using Slashes in Alternate Encoding
This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.