CWE-22
Weakness Allowed-with-ReviewImproper Limitation of a Pathname to a Restricted Directory
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.
Many file operations are intended to take place within a restricted directory. By using special elements such as ".." and "/" separators, attackers can escape outside of the restricted location to access files or directories that are elsewhere on the system. One of the most common special elements is the "../" sequence, which in most modern operating systems is interpreted as the parent directory of the current location. This is referred to as relative path traversal. Path traversal also covers the use of absolute pathnames such as "/usr/local/bin" to access unexpected files. This is referred to as absolute path traversal.
Mapping guidance
This CWE entry might have children that would be more appropriate.
Examine children of this entry to see if there is a better fit. Consider children such as CWE-23 (or its descendants) for relative path traversal, or CWE-36 for absolute path traversal.
Relationships and members
Modes of introduction
Detection methods
Automated Static Analysis
Automated techniques can find areas where path traversal weaknesses exist. However, tuning or customization may be required to remove or de-prioritize path-traversal problems that are only exploitable by the product's administrator - or other privileged users - and thus potentially valid behavior or, at worst, a bug instead of a vulnerability.
Effectiveness: High
Manual Static Analysis
Manual white box techniques may be able to provide sufficient code coverage and reduction of false positives if all file access operations can be assessed within limited time constraints.
Effectiveness: High
Automated Static Analysis - Binary or Bytecode
According to SOAR [REF-1479], the following detection techniques may be useful:
Highly cost effective:
Bytecode Weakness Analysis - including disassembler + source code weakness analysis
Cost effective for partial coverage:
Binary Weakness Analysis - including disassembler + source code weakness analysis
Effectiveness: High
Manual Static Analysis - Binary or Bytecode
According to SOAR [REF-1479], the following detection techniques may be useful:
Cost effective for partial coverage:
Binary / Bytecode disassembler - then use manual analysis for vulnerabilities & anomalies
Effectiveness: SOAR Partial
Dynamic Analysis with Automated Results Interpretation
According to SOAR [REF-1479], the following detection techniques may be useful:
Highly cost effective:
Web Application Scanner
Web Services Scanner
Database Scanners
Effectiveness: High
Dynamic Analysis with Manual Results Interpretation
According to SOAR [REF-1479], the following detection techniques may be useful:
Highly cost effective:
Fuzz Tester
Framework-based Fuzzer
Effectiveness: High
Manual Static Analysis - Source Code
According to SOAR [REF-1479], the following detection techniques may be useful:
Highly cost effective:
Manual Source Code Review (not inspections)
Cost effective for partial coverage:
Focused Manual Spotcheck - Focused manual analysis of source
Effectiveness: High
Automated Static Analysis - Source Code
According to SOAR [REF-1479], the following detection techniques may be useful:
Highly cost effective:
Source code Weakness Analyzer
Context-configured Source Code Weakness Analyzer
Effectiveness: High
Architecture or Design Review
According to SOAR [REF-1479], the following detection techniques may be useful:
Highly cost effective:
Formal Methods / Correct-By-Construction
Cost effective for partial coverage:
Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)
Effectiveness: High
Notes
Other
In many programming languages, the injection of a null byte (the 0 or NUL) may allow an attacker to truncate a generated filename to apply to a wider range of files. For example, the product may add ".txt" to any pathname, thus limiting the attacker to text files, but a null injection may effectively remove this restriction.
Relationship
Pathname equivalence can be regarded as a type of canonicalization error.
Relationship
Some pathname equivalence issues are not directly related to directory traversal, rather are used to bypass security-relevant checks for whether a file/directory can be accessed by the attacker (e.g. a trailing "/" on a filename could bypass access rules that don't expect a trailing /, causing a server to provide the file when it normally would not).
Terminology
Like other weaknesses, terminology is often based on the types of manipulations used, instead of the underlying weaknesses. Some people use "directory traversal" only to refer to the injection of ".." and equivalent sequences whose specific meaning is to traverse directories.
Other variants like "absolute pathname" and "drive letter" have the *effect* of directory traversal, but some people may not call it such, since it doesn't involve ".." or equivalent.
Research Gap
Many variants of path traversal attacks are probably under-studied with respect to root cause. CWE-790 and CWE-182 begin to cover part of this gap.
Research Gap
Incomplete diagnosis or reporting of vulnerabilities can make it difficult to know which variant is affected. For example, a researcher might say that "..\" is vulnerable, but not test "../" which may also be vulnerable.
Any combination of directory separators ("/", "\", etc.) and numbers of "." (e.g. "....") can produce unique variants; for example, the "//../" variant is not listed (CVE-2004-0325). See this entry's children and lower-level descendants.
Content history
Identified weakness in Perl demonstrative example
Provided diagram to improve CWE usability
Identified weakness in "good code" for Python demonstrative example
Provided a demonstrative example in PHP
updated Potential_Mitigations, Time_of_Introduction
Suggested OWASP Top Ten 2004 mapping
updated Alternate_Terms, Relationships, Other_Notes, Relationship_Notes, Relevant_Properties, Taxonomy_Mappings, Weakness_Ordinalities
updated Description
updated Relationships, Taxonomy_Mappings
updated Potential_Mitigations
updated Alternate_Terms, Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Likelihood_of_Exploit, Name, Observed_Examples, Other_Notes, Potential_Mitigations, References, Related_Attack_Patterns, Relationship_Notes, Relationships, Research_Gaps, Taxonomy_Mappings, Terminology_Notes, Time_of_Introduction, Weakness_Ordinalities
updated Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Potential_Mitigations, References, Relationships
updated Potential_Mitigations
updated Potential_Mitigations
updated Potential_Mitigations
updated Relationships
updated Potential_Mitigations, References, Relationships, Taxonomy_Mappings
updated Demonstrative_Examples, References, Relationships
updated Potential_Mitigations
updated Observed_Examples
updated Related_Attack_Patterns, Relationships
updated Other_Notes, Research_Gaps
updated Detection_Factors, Relationships, Taxonomy_Mappings
updated Relationships
updated Related_Attack_Patterns
updated Demonstrative_Examples
updated Affected_Resources, Causal_Nature, Likelihood_of_Exploit, References, Relationships, Relevant_Properties, Taxonomy_Mappings
updated References, Relationships
updated References, Related_Attack_Patterns, Relationships, Taxonomy_Mappings
updated Related_Attack_Patterns, Relationships, Type
updated Relationships
updated Potential_Mitigations, Relationships
updated Demonstrative_Examples, Potential_Mitigations
updated Relationships
updated Potential_Mitigations, Relationships
updated Demonstrative_Examples, Relationships
updated Relationships
updated Observed_Examples, Relationships
updated Observed_Examples, Relationships
updated Observed_Examples, References
updated Common_Consequences, Description, Detection_Factors
updated Demonstrative_Examples, References, Relationships, Time_of_Introduction
updated Mapping_Notes, Relationships
updated Observed_Examples
updated Common_Consequences, Description, Diagram, Observed_Examples, Other_Notes, References
updated Demonstrative_Examples, Relationships
updated Relationships
updated Applicable_Platforms, Detection_Factors, Observed_Examples, Potential_Mitigations, References
updated Mapping_Notes, Relationships
updated Alternate_Terms, Applicable_Platforms, Demonstrative_Examples, Relationships
updated Applicable_Platforms, Common_Consequences, Name, References, Relationships, Taxonomy_Mappings
16155 vulnerabilities reference this CWE, most recent first.
GHSA-586J-JR5F-GX4J
Vulnerability from github – Published: 2026-04-14 18:30 – Updated: 2026-04-22 15:31CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability exists that could cause critical files overwritten with text data when a Web Admin user alters the POST /REST/upssleep request payload.
{
"affected": [],
"aliases": [
"CVE-2026-2399"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-04-14T16:16:38Z",
"severity": "MODERATE"
},
"details": "CWE-22 Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027) vulnerability exists that could cause critical files overwritten with text data when a Web Admin user alters the POST /REST/upssleep request payload.",
"id": "GHSA-586j-jr5f-gx4j",
"modified": "2026-04-22T15:31:32Z",
"published": "2026-04-14T18:30:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2399"
},
{
"type": "WEB",
"url": "https://download.schneider-electric.com/files?p_Doc_Ref=SEVD-2026-104-01\u0026p_enDocType=Security+and+Safety+Notice\u0026p_File_Name=SEVD-2026-104-01.pdf"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/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-586P-749J-FHWP
Vulnerability from github – Published: 2024-10-09 15:32 – Updated: 2026-10-30 18:32A vulnerability was found in Buildah. Cache mounts do not properly validate that user-specified paths for the cache are within our cache directory, allowing a RUN instruction in a Container file to mount an arbitrary directory from the host (read/write) into the container as long as those files can be accessed by the user running Buildah.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/containers/buildah"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.38.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-9675"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2024-10-09T19:15:02Z",
"nvd_published_at": "2024-10-09T15:15:17Z",
"severity": "MODERATE"
},
"details": "A vulnerability was found in Buildah. Cache mounts do not properly validate that user-specified paths for the cache are within our cache directory, allowing a `RUN` instruction in a Container file to mount an arbitrary directory from the host (read/write) into the container as long as those files can be accessed by the user running Buildah.",
"id": "GHSA-586p-749j-fhwp",
"modified": "2026-10-30T18:32:15Z",
"published": "2024-10-09T15:32:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-9675"
},
{
"type": "WEB",
"url": "https://github.com/containers/buildah/commit/aa67e5d71ee7ec07122a210baa3b13966a9e086c"
},
{
"type": "WEB",
"url": "https://pkg.go.dev/vuln/GO-2024-3186"
},
{
"type": "PACKAGE",
"url": "https://github.com/containers/buildah"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2317458"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2024-9675"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:3573"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:3301"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:2710"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:2701"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:2454"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:2449"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:2445"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:9459"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:9454"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:9051"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8994"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8984"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8846"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8709"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8708"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8707"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8703"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8700"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8690"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8686"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8679"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8675"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2024:8563"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHEA-2024:6126"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHBA-2024:10967"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Buildah allows arbitrary directory mount"
}
GHSA-586V-XV8V-GC4W
Vulnerability from github – Published: 2022-05-04 00:29 – Updated: 2022-05-04 00:29Directory traversal vulnerability in the Manager service in the management console in Symantec Endpoint Protection (SEP) 12.1 before 12.1 RU1-MP1 allows remote attackers to delete files via unspecified vectors.
{
"affected": [],
"aliases": [
"CVE-2012-0294"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2012-05-23T21:55:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in the Manager service in the management console in Symantec Endpoint Protection (SEP) 12.1 before 12.1 RU1-MP1 allows remote attackers to delete files via unspecified vectors.",
"id": "GHSA-586v-xv8v-gc4w",
"modified": "2022-05-04T00:29:16Z",
"published": "2022-05-04T00:29:16Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2012-0294"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/53182"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id?1027093"
},
{
"type": "WEB",
"url": "http://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory\u0026pvid=security_advisory\u0026year=2012\u0026suid=20120522_01"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-5879-4FMR-XWF2
Vulnerability from github – Published: 2026-04-14 23:21 – Updated: 2026-04-24 20:40Summary
The incomplete fix for AVideo's CloneSite deleteDump parameter does not apply path traversal filtering, allowing unlink() of arbitrary files via ../../ sequences in the GET parameter.
Affected Package
- Ecosystem: Other
- Package: AVideo
- Affected versions: < commit 941decd6d19e
- Patched versions: >= commit 941decd6d19e
Details
At line 44-48 of cloneServer.json.php (pre-fix):
if (!empty($_GET['deleteDump'])) {
$resp->error = !unlink("{$clonesDir}{$_GET['deleteDump']}");
$resp->msg = "Delete Dump {$_GET['deleteDump']}";
die(json_encode($resp));
}
No basename(), no realpath() check, no path traversal filtering. $_GET['deleteDump'] is concatenated directly with $clonesDir.
The vulnerable code has zero protection against path traversal:
- No basename() to strip directory components
- No realpath() to validate the final path
- No check that resolved path is within $clonesDir
- No ../ sanitization
- Additionally, exec() calls with mysqldump pass credentials on the command line
PoC
"""
CVE-2026-33293 - AVideo CloneSite Path Traversal
"""
import sys
import os
VULN_SRC = os.path.join(os.path.dirname(__file__), "src", "cloneServer.json.php")
def verify_source_file():
if not os.path.isfile(VULN_SRC):
print("ERROR: Source not found at %s" % VULN_SRC)
sys.exit(1)
with open(VULN_SRC, "r") as f:
src = f.read()
if "unlink(" not in src or "deleteDump" not in src:
print("ERROR: Expected patterns not found")
sys.exit(1)
return src
def vulnerable_delete_path(clones_dir, delete_dump):
return clones_dir + delete_dump
def test_path_traversal():
clones_dir = "/var/www/html/AVideo/videos/clones/"
payloads = [
("../../configuration.php", "Delete site configuration"),
("../../../etc/passwd", "Delete system file"),
("../../.htaccess", "Delete .htaccess"),
]
print("Testing path traversal via deleteDump parameter:")
print("Base clones_dir: %s" % clones_dir)
print()
all_traversal = True
for payload, desc in payloads:
resolved = vulnerable_delete_path(clones_dir, payload)
real_resolved = os.path.normpath(resolved)
escaped = not real_resolved.startswith(os.path.normpath(clones_dir))
if escaped:
print("[+] TRAVERSAL: %s" % desc)
print(" Payload: deleteDump=%s" % payload)
print(" unlink() target: %s" % resolved)
print(" Normalized: %s" % real_resolved)
else:
all_traversal = False
return all_traversal
def main():
print("=" * 70)
print("CVE-2026-33293: AVideo CloneSite Path Traversal PoC")
print("=" * 70)
print()
src = verify_source_file()
print("[+] Source file verified: %s" % VULN_SRC)
for line in src.split('\n'):
if 'unlink(' in line and 'deleteDump' in line:
print("[+] Vulnerable line: %s" % line.strip())
break
print()
if test_path_traversal():
print("\nVULNERABILITY CONFIRMED")
sys.exit(0)
else:
print("\nVULNERABILITY NOT CONFIRMED")
sys.exit(1)
if __name__ == "__main__":
main()
python3 poc.py
Steps to reproduce:
1. git clone https://github.com/WWBN/AVideo /tmp/AVideo_test
2. cd /tmp/AVideo_test && git checkout 941decd6d19e2e694acb75e86317d10fbb560284~1
3. python3 poc.py
Expected output:
VULNERABILITY CONFIRMED
The deleteDump parameter passes unsanitized path traversal sequences (../../) directly to unlink(), enabling arbitrary file deletion.
Impact
An attacker can delete arbitrary files on the server. Deleting configuration.php takes the site offline. Deleting .htaccess exposes protected directories. Deleting system files can affect other services.
Suggested Remediation
Use basename($_GET['deleteDump']) to strip directory components. Validate that realpath() of the final path is within $clonesDir. Validate file extension. Add authentication checks.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "wwbn/avideo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "29.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-41058"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-14T23:21:31Z",
"nvd_published_at": "2026-04-21T23:16:21Z",
"severity": "MODERATE"
},
"details": "### Summary\n\nThe incomplete fix for AVideo\u0027s CloneSite `deleteDump` parameter does not apply path traversal filtering, allowing `unlink()` of arbitrary files via `../../` sequences in the GET parameter.\n\n### Affected Package\n\n- **Ecosystem:** Other\n- **Package:** AVideo\n- **Affected versions:** \u003c commit 941decd6d19e\n- **Patched versions:** \u003e= commit 941decd6d19e\n\n### Details\n\nAt line 44-48 of `cloneServer.json.php` (pre-fix):\n```php\nif (!empty($_GET[\u0027deleteDump\u0027])) {\n $resp-\u003eerror = !unlink(\"{$clonesDir}{$_GET[\u0027deleteDump\u0027]}\");\n $resp-\u003emsg = \"Delete Dump {$_GET[\u0027deleteDump\u0027]}\";\n die(json_encode($resp));\n}\n```\n\nNo `basename()`, no `realpath()` check, no path traversal filtering. `$_GET[\u0027deleteDump\u0027]` is concatenated directly with `$clonesDir`.\n\nThe vulnerable code has zero protection against path traversal:\n- No `basename()` to strip directory components\n- No `realpath()` to validate the final path\n- No check that resolved path is within `$clonesDir`\n- No `../` sanitization\n- Additionally, `exec()` calls with `mysqldump` pass credentials on the command line\n\n### PoC\n\n```python\n\"\"\"\nCVE-2026-33293 - AVideo CloneSite Path Traversal\n\"\"\"\n\nimport sys\nimport os\n\nVULN_SRC = os.path.join(os.path.dirname(__file__), \"src\", \"cloneServer.json.php\")\n\ndef verify_source_file():\n if not os.path.isfile(VULN_SRC):\n print(\"ERROR: Source not found at %s\" % VULN_SRC)\n sys.exit(1)\n with open(VULN_SRC, \"r\") as f:\n src = f.read()\n if \"unlink(\" not in src or \"deleteDump\" not in src:\n print(\"ERROR: Expected patterns not found\")\n sys.exit(1)\n return src\n\ndef vulnerable_delete_path(clones_dir, delete_dump):\n return clones_dir + delete_dump\n\ndef test_path_traversal():\n clones_dir = \"/var/www/html/AVideo/videos/clones/\"\n payloads = [\n (\"../../configuration.php\", \"Delete site configuration\"),\n (\"../../../etc/passwd\", \"Delete system file\"),\n (\"../../.htaccess\", \"Delete .htaccess\"),\n ]\n\n print(\"Testing path traversal via deleteDump parameter:\")\n print(\"Base clones_dir: %s\" % clones_dir)\n print()\n\n all_traversal = True\n for payload, desc in payloads:\n resolved = vulnerable_delete_path(clones_dir, payload)\n real_resolved = os.path.normpath(resolved)\n escaped = not real_resolved.startswith(os.path.normpath(clones_dir))\n\n if escaped:\n print(\"[+] TRAVERSAL: %s\" % desc)\n print(\" Payload: deleteDump=%s\" % payload)\n print(\" unlink() target: %s\" % resolved)\n print(\" Normalized: %s\" % real_resolved)\n else:\n all_traversal = False\n\n return all_traversal\n\ndef main():\n print(\"=\" * 70)\n print(\"CVE-2026-33293: AVideo CloneSite Path Traversal PoC\")\n print(\"=\" * 70)\n print()\n\n src = verify_source_file()\n print(\"[+] Source file verified: %s\" % VULN_SRC)\n\n for line in src.split(\u0027\\n\u0027):\n if \u0027unlink(\u0027 in line and \u0027deleteDump\u0027 in line:\n print(\"[+] Vulnerable line: %s\" % line.strip())\n break\n print()\n\n if test_path_traversal():\n print(\"\\nVULNERABILITY CONFIRMED\")\n sys.exit(0)\n else:\n print(\"\\nVULNERABILITY NOT CONFIRMED\")\n sys.exit(1)\n\nif __name__ == \"__main__\":\n main()\n```\n\n```bash\npython3 poc.py\n```\n\n**Steps to reproduce:**\n1. `git clone https://github.com/WWBN/AVideo /tmp/AVideo_test`\n2. `cd /tmp/AVideo_test \u0026\u0026 git checkout 941decd6d19e2e694acb75e86317d10fbb560284~1`\n3. `python3 poc.py`\n\n**Expected output:**\n```\nVULNERABILITY CONFIRMED\nThe deleteDump parameter passes unsanitized path traversal sequences (../../) directly to unlink(), enabling arbitrary file deletion.\n```\n\n### Impact\n\nAn attacker can delete arbitrary files on the server. Deleting `configuration.php` takes the site offline. Deleting `.htaccess` exposes protected directories. Deleting system files can affect other services.\n\n### Suggested Remediation\n\nUse `basename($_GET[\u0027deleteDump\u0027])` to strip directory components. Validate that `realpath()` of the final path is within `$clonesDir`. Validate file extension. Add authentication checks.",
"id": "GHSA-5879-4fmr-xwf2",
"modified": "2026-04-24T20:40:51Z",
"published": "2026-04-14T23:21:31Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-5879-4fmr-xwf2"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-xmjm-86qv-g226"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33293"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-41058"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/commit/3c729717c26f160014a5c86b0b6accdbd613e7b2"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/commit/941decd6d19e2e694acb75e86317d10fbb560284"
},
{
"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:N/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "WWBN AVideo has an incomplete fix for CVE-2026-33293: Path Traversal"
}
GHSA-589V-64M6-5JFC
Vulnerability from github – Published: 2022-05-14 01:40 – Updated: 2022-05-14 01:40Directory traversal vulnerability in Cybozu Office 10.0.0 to 10.8.1 allows remote attackers to delete arbitrary files via HTTP requests.
{
"affected": [],
"aliases": [
"CVE-2018-0703"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-01-09T23:29:00Z",
"severity": "HIGH"
},
"details": "Directory traversal vulnerability in Cybozu Office 10.0.0 to 10.8.1 allows remote attackers to delete arbitrary files via HTTP requests.",
"id": "GHSA-589v-64m6-5jfc",
"modified": "2022-05-14T01:40:48Z",
"published": "2022-05-14T01:40:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-0703"
},
{
"type": "WEB",
"url": "https://jvn.jp/en/jp/JVN15232217/index.html"
},
{
"type": "WEB",
"url": "https://kb.cybozu.support/article/34088"
}
],
"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-58C4-H2GX-8QFV
Vulnerability from github – Published: 2024-05-21 21:30 – Updated: 2024-05-21 21:30There are multiple ways in LCDS LAquis SCADA for an attacker to access locations outside of their own directory.
{
"affected": [],
"aliases": [
"CVE-2024-5040"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-05-21T21:15:08Z",
"severity": "HIGH"
},
"details": "There are multiple ways in \nLCDS LAquis SCADA for an attacker to access locations outside of their own directory.",
"id": "GHSA-58c4-h2gx-8qfv",
"modified": "2024-05-21T21:30:28Z",
"published": "2024-05-21T21:30:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-5040"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/news-events/ics-advisories/icsa-24-142-01"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-58F3-75GM-GVGR
Vulnerability from github – Published: 2022-05-02 06:23 – Updated: 2022-05-02 06:23Directory traversal vulnerability in WebAsyst Shop-Script FREE has unknown impact and attack vectors via the sub parameter.
{
"affected": [],
"aliases": [
"CVE-2010-1462"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2010-04-16T19:30:00Z",
"severity": "HIGH"
},
"details": "Directory traversal vulnerability in WebAsyst Shop-Script FREE has unknown impact and attack vectors via the sub parameter.",
"id": "GHSA-58f3-75gm-gvgr",
"modified": "2022-05-02T06:23:00Z",
"published": "2022-05-02T06:23:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2010-1462"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/510741/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2010/0882"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/research-web.php"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-58FP-MCX6-7QF9
Vulnerability from github – Published: 2026-08-20 18:43 – Updated: 2026-08-20 18:43Impact
Affected versions of Winter CMS allow authenticated backend users with the following permissions to disclose arbitrary files readable by the PHP process by injecting @import (inline) "<path>" directives into LESS source that the backend compiles. Four entry points share the same root cause:
- Brand Settings
BrandSetting.custom_cssfield (backend.manage_branding) — compiled inline into every backend page's<style>block. - Editor Settings
EditorSetting.html_custom_stylesfield (backend.manage_editor) — compiled inline into every backend page's<style>block. - Mail Brand Settings
MailBrandSettingcolour-picker fields (system.manage_mail_templates) — values are concatenated into LESS source viaLess_Parser::ModifyVars()with no escaping, so any value the form validator does not reject can carry an@importdirective. - Theme
.less/.sass/.scssassets (cms.manage_assets) — compiled throughSystem\Classes\CombineAssetswhen served, with the sameLess_Parserconfiguration. Both absolute paths and..traversal escape from the asset's own tree were exploitable.
The leaked content includes any file the web process can read, most importantly the application .env file (disclosing APP_KEY and database credentials).
To actively exploit this issue, an attacker would need an authenticated backend account with one of the permissions listed above. By default these are assigned to the built-in Developer role.
Patches
The root cause is in the wikimedia/less.php integration in Winter Storm: Less_Parser was instantiated without a safe import resolver, and its Less_FileManager::getFilePath() falls back to the raw attacker-supplied path when no candidate root matches. Storm now ships a LessImportResolver that uses the callable form of Less_Parser::SetImportDirs() to refuse any @import whose resolved path lies outside the calling context's allowed roots, defeating both absolute paths and .. traversal at the parser level.
The four sinks have been updated to use the resolver. The three settings models pass no allowed roots (deny-all) because the bundled stylesheets ship no @import directives and the user fields have no legitimate use for them. System\Classes\CombineAssets configures the theme-asset compiler with themes_path(), plugins_path(), and base_path('modules') as allowed roots, preserving real cross-tree imports observed in shipped themes and plugins.
This security issue has been fixed in v1.2.13 (Winter core) and v1.2.13 (Winter Storm).
Workarounds
If you cannot upgrade, apply https://github.com/wintercms/storm/commit/af770331c683e628533a6ec2991285d6e10a4d6c and https://github.com/wintercms/winter/commit/130f0ea43e9228bf0d129b481da1cdfbcc4b4456 manually. As an interim mitigation, remove cms.manage_assets from any non-trusted role and clear any non-empty value from the Brand Settings custom_css and Editor Settings html_custom_styles fields.
References
See https://github.com/octobercms/october/security/advisories/GHSA-3888-q23f-x7qh for the related (but distinct in scope) October CMS advisory addressing the theme-asset compiler path. The Brand/Editor/Mail Brand Settings sinks reported in this advisory are not covered by the October patch.
Credit to Nguyen Van Hiep (@hypnguyen1209) from Lo Security for reporting the issue.
For more information
If you have any questions or comments about this advisory: - Email us at hello@wintercms.com
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.2.12"
},
"package": {
"ecosystem": "Packagist",
"name": "winter/wn-backend-module"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.2.13"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-63179"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": true,
"github_reviewed_at": "2026-08-20T18:43:33Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "### Impact\n\nAffected versions of Winter CMS allow authenticated backend users with the following permissions to disclose arbitrary files readable by the PHP process by injecting `@import (inline) \"\u003cpath\u003e\"` directives into LESS source that the backend compiles. Four entry points share the same root cause:\n\n- **Brand Settings** `BrandSetting.custom_css` field (`backend.manage_branding`) \u2014 compiled inline into every backend page\u0027s `\u003cstyle\u003e` block.\n- **Editor Settings** `EditorSetting.html_custom_styles` field (`backend.manage_editor`) \u2014 compiled inline into every backend page\u0027s `\u003cstyle\u003e` block.\n- **Mail Brand Settings** `MailBrandSetting` colour-picker fields (`system.manage_mail_templates`) \u2014 values are concatenated into LESS source via `Less_Parser::ModifyVars()` with no escaping, so any value the form validator does not reject can carry an `@import` directive.\n- **Theme `.less`/`.sass`/`.scss` assets** (`cms.manage_assets`) \u2014 compiled through `System\\Classes\\CombineAssets` when served, with the same `Less_Parser` configuration. Both absolute paths and `..` traversal escape from the asset\u0027s own tree were exploitable.\n\nThe leaked content includes any file the web process can read, most importantly the application `.env` file (disclosing `APP_KEY` and database credentials).\n\nTo actively exploit this issue, an attacker would need an authenticated backend account with one of the permissions listed above. By default these are assigned to the built-in Developer role.\n\n### Patches\n\nThe root cause is in the `wikimedia/less.php` integration in [Winter Storm](https://github.com/wintercms/storm): `Less_Parser` was instantiated without a safe import resolver, and its `Less_FileManager::getFilePath()` falls back to the raw attacker-supplied path when no candidate root matches. Storm now ships a `LessImportResolver` that uses the callable form of `Less_Parser::SetImportDirs()` to refuse any `@import` whose resolved path lies outside the calling context\u0027s allowed roots, defeating both absolute paths and `..` traversal at the parser level.\n\nThe four sinks have been updated to use the resolver. The three settings models pass no allowed roots (deny-all) because the bundled stylesheets ship no `@import` directives and the user fields have no legitimate use for them. `System\\Classes\\CombineAssets` configures the theme-asset compiler with `themes_path()`, `plugins_path()`, and `base_path(\u0027modules\u0027)` as allowed roots, preserving real cross-tree imports observed in shipped themes and plugins.\n\nThis security issue has been fixed in [v1.2.13](https://github.com/wintercms/winter/commit/130f0ea43e9228bf0d129b481da1cdfbcc4b4456) (Winter core) and [v1.2.13](https://github.com/wintercms/storm/commit/af770331c683e628533a6ec2991285d6e10a4d6c) (Winter Storm).\n\n### Workarounds\n\nIf you cannot upgrade, apply https://github.com/wintercms/storm/commit/af770331c683e628533a6ec2991285d6e10a4d6c and https://github.com/wintercms/winter/commit/130f0ea43e9228bf0d129b481da1cdfbcc4b4456 manually. As an interim mitigation, remove `cms.manage_assets` from any non-trusted role and clear any non-empty value from the Brand Settings `custom_css` and Editor Settings `html_custom_styles` fields.\n\n### References\n\nSee https://github.com/octobercms/october/security/advisories/GHSA-3888-q23f-x7qh for the related (but distinct in scope) October CMS advisory addressing the theme-asset compiler path. The Brand/Editor/Mail Brand Settings sinks reported in this advisory are not covered by the October patch.\n\nCredit to Nguyen Van Hiep ([@hypnguyen1209](https://github.com/hypnguyen1209)) from Lo Security for reporting the issue.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n- Email us at [hello@wintercms.com](mailto:hello@wintercms.com)",
"id": "GHSA-58fp-mcx6-7qf9",
"modified": "2026-08-20T18:43:33Z",
"published": "2026-08-20T18:43:33Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/wintercms/winter/security/advisories/GHSA-58fp-mcx6-7qf9"
},
{
"type": "WEB",
"url": "https://github.com/wintercms/storm/commit/af770331c683e628533a6ec2991285d6e10a4d6c"
},
{
"type": "WEB",
"url": "https://github.com/wintercms/winter/commit/130f0ea43e9228bf0d129b481da1cdfbcc4b4456"
},
{
"type": "PACKAGE",
"url": "https://github.com/wintercms/winter"
},
{
"type": "WEB",
"url": "https://github.com/wintercms/winter/releases/tag/v1.2.13"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Winter: Local File Inclusion through @import directives in LESS compilation of backend customizable stylesheets and theme assets"
}
GHSA-58GM-G38V-XCH5
Vulnerability from github – Published: 2022-05-02 03:45 – Updated: 2022-05-02 03:45Directory traversal vulnerability in WebCoreModule.ashx in RADactive I-Load before 2008.2.5.0 allows remote attackers to read arbitrary files via unspecified vectors.
{
"affected": [],
"aliases": [
"CVE-2009-3451"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-09-29T15:30:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in WebCoreModule.ashx in RADactive I-Load before 2008.2.5.0 allows remote attackers to read arbitrary files via unspecified vectors.",
"id": "GHSA-58gm-g38v-xch5",
"modified": "2022-05-02T03:45:12Z",
"published": "2022-05-02T03:45:12Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-3451"
},
{
"type": "WEB",
"url": "https://www.sec-consult.com/files/20090917-0_RADactive_I-Load_Multiple_Vulnerabilities.txt"
},
{
"type": "WEB",
"url": "http://radnet.radactive.com/forum/Default.aspx?g=posts\u0026t=339"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/23807"
},
{
"type": "WEB",
"url": "http://www.osvdb.org/58196"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/506555/100/0/threaded"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-58GX-PMMM-W878
Vulnerability from github – Published: 2022-05-17 00:45 – Updated: 2022-05-17 00:45Directory traversal vulnerability in modules/download/get_file.php in Admidio 1.4.8 allows remote attackers to read arbitrary files via a .. (dot dot) in the file parameter.
{
"affected": [],
"aliases": [
"CVE-2008-5209"
],
"database_specific": {
"cwe_ids": [
"CWE-22"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2008-11-24T17:30:00Z",
"severity": "MODERATE"
},
"details": "Directory traversal vulnerability in modules/download/get_file.php in Admidio 1.4.8 allows remote attackers to read arbitrary files via a .. (dot dot) in the file parameter.",
"id": "GHSA-58gx-pmmm-w878",
"modified": "2022-05-17T00:45:02Z",
"published": "2022-05-17T00:45:02Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2008-5209"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/42304"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/5575"
},
{
"type": "WEB",
"url": "http://securityreason.com/securityalert/4625"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/29127"
}
],
"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.