CVE-2024-6746
Path Traversal in Easyspider 0.6.2
Raw vector
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/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:XSummary
CVE-2024-6746 is a medium-severity Path Traversal: '../filedir' (CWE-24) vulnerability in Easyspider Easyspider. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 13% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-6746 is a path traversal vulnerability in NaiboWang EasySpider version 0.6.2 on Windows. It resides in the HTTP GET Request Handler within the file EasySpider/resources/app/server.js, where unsanitized input such as /../../../../../../../../../Windows/win.ini can be supplied to traverse directories and access arbitrary files on the host.
An attacker on the local network can exploit the flaw without authentication or user interaction to read sensitive files outside the application's intended scope. The vulnerability has been publicly disclosed, and proof-of-concept details are available, enabling any adjacent adversary to retrieve configuration or system files such as win.ini.
The project maintainer has stated that the issue is limited in impact because the software is intended to run locally without exposure to the Internet. No official patches or configuration changes are referenced in the available advisories.
The associated EPSS score currently stands at 0.81 with a recorded peak of 0.8226, indicating sustained exploitation interest following disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-47783
Vulnerability Data
A vulnerability classified as problematic was found in NaiboWang EasySpider 0.6.2 on Windows. Affected by this vulnerability is an unknown functionality of the file \EasySpider\resources\app\server.js of the component HTTP GET Request Handler. The manipulation with the input /../../../../../../../../../Windows/win.ini leads to…
more
path traversal: '../filedir'. The attack needs to be done within the local network. The exploit has been disclosed to the public and may be used. The identifier VDB-271477 was assigned to this vulnerability. NOTE: The code maintainer explains, that this is not a big issue "because the default is that the software runs locally without going through the Internet".
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes '../' sequences in externally-supplied pathnames before they are resolved.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and path sanitization that prevent ../ traversal.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards require neutralizing ../ sequences and canonicalizing paths before file operations.
Security testing in development catches path-traversal flaws before release.
Secure SDLC mandates input validation and path canonicalization that directly block ../ traversal.
Application security requirements explicitly call for controls against path traversal in file-handling functions.
Secure architecture principles reduce attack surface but do not prescribe the specific coding fix.
Information access restriction limits which files can be reached, mitigating impact of traversal.