CVE-2001-0404
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDirectory traversal vulnerability in JavaServer Web Dev Kit (JSWDK) 1.0.1 allows remote attackers to read arbitrary files via a .. (dot dot) in an HTTP request to the WEB-INF directory.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJSWDK 1.0.1 contains a directory traversal vulnerability where an attacker can use '..' sequences in HTTP requests targeting the WEB-INF directory to access files outside the web root, potentially exposing sensitive configuration files, source code, or other system files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify JSWDK installationCheck if the JavaServer Web Development Kit (JSWDK) is installed on the system by searching for JSWDK directories or checking installed packages. Common locations include /opt/JSWDK or C:\Program Files\JSWDK on Windows.Affected if JSWDK version 1.0.1 is found installed on the system
-
Confirm the specific versionLocate the version file or About information within the JSWDK installation directory to confirm the exact version number.Affected if The installed version is exactly 1.0.1
-
Identify web root locationFind the web root or document root directory configured for the JSWDK web server, typically found in the server's configuration files or the default 'webpages' or 'public_html' subdirectory within the JSWDK installation.Affected if A web root directory exists and is served by JSWDK 1.0.1
-
Check WEB-INF accessibilityVerify that the WEB-INF directory exists within a web application and is accessible via HTTP by attempting to access it through the web server.Affected if WEB-INF directory is accessible via HTTP requests
-
Test for directory traversalSend an HTTP GET request to the web server using a path like /WEB-INF/../../../etc/passwd or similar to test if directory traversal sequences are processed without proper validation.Affected if The server returns files from outside the web root when '..' sequences are used in the request path
The environment is affected if JSWDK version 1.0.1 is running and the web server allows directory traversal via '..' sequences in requests to access files outside the web root.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of JSWDK or migrate to a supported servlet container. If upgrade is not feasible, implement input validation filters to reject requests containing '..' sequences and restrict file system permissions on the web root.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-0404 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2001-0404 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data