dbcve.org
Websphere Commerce SuiteApplication · Ibm

CVE-2001-0446

MEDIUM · 5.0 CVSS v2.0 Published 2001-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
IBM WCS (WebSphere Commerce Suite) 4.0.1 with Application Server 3.0.2 allows remote attackers to read source code for .jsp files by appending a / to the requested URL.

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 confidence

IBM WebSphere Commerce Suite 4.0.1 with Application Server 3.0.2 contains a path traversal vulnerability that allows remote attackers to read JSP source code by appending a trailing slash (/) to the requested URL. This results in information disclosure of potentially sensitive application source code.

MitigationUpgrade to a supported version of IBM WebSphere Commerce Suite and Application Server, as version 4.0.1/3.0.2 is obsolete. Alternatively, configure the web server to deny access to source code files or implement URL rewriting rules to block trailing slash exploitation attempts.

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
Websphere Commerce SuiteApplication
Affected:= 4.0.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM WebSphere Commerce Suite version
    Check the installed version by inspecting the product documentation, registry, or running: 'lslpp -l | grep -i websphere' on AIX, or checking the installation directory for version files. Look for files named 'version.txt', 'manifest.mf', or check the IBM WebSphere administration console for the version information.
    Affected if The installed version is IBM WebSphere Commerce Suite 4.0.1 specifically.
  2. Confirm Application Server component version
    Check the bundled WebSphere Application Server version. Look in the 'AppServer' or 'was' subdirectory of the Commerce Suite installation. The administration console or logs typically display the Application Server version on startup.
    Affected if The Application Server version is 3.0.2.
  3. Verify JSP handling is enabled
    Check if JSP file handling is configured in the web server. Look for servlet engine configuration files (such as 'servlets.xml' or 'web.xml') in the Application Server configuration directory that enable JSP servlet mapping.
    Affected if JSP servlet mapping is enabled and JSP files are being served by the web application.
  4. Test for trailing slash path traversal
    Make an HTTP request to a known JSP file on the server with a trailing slash appended. For example: GET /somepage.jsp/ HTTP/1.1. Use curl or a browser to request a JSP file in a web-accessible directory with a trailing slash.
    Affected if The server returns the JSP source code (not executed) instead of a 404 error or executed output.
  5. Check web server configuration for source code exposure
    Inspect the IBM HTTP Server (or other web server) configuration for MIME type handlers. Look in httpd.conf or ibmhttpd.conf for JSP handler mappings. Verify if the server is configured to serve .jsp files as plain text instead of executing them.
    Affected if The web server serves .jsp files as text/plain or application/java instead of executing them through the servlet engine.

The environment is affected if IBM WebSphere Commerce Suite version 4.0.1 with Application Server 3.0.2 is installed and the web server serves JSP files, allowing source code disclosure via trailing slash requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a supported version of IBM WebSphere Commerce Suite and Application Server, as version 4.0.1/3.0.2 is obsolete. Alternatively, configure the web server to deny access to source code files or implement URL rewriting rules to block trailing slash exploitation attempts.

Fix this in Websphere Commerce Suite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing2.0 h
  • Review / QA1.0 h
13.0 hours of engineering $2,320
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,712.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2001-0446 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2001-0446 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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