CVE-2002-1987
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 view_source.jsp in Resin 2.1.2 allows remote attackers to read arbitrary files via a "\.." (backslash dot dot).
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 confidenceDirectory traversal vulnerability in view_source.jsp in Resin 2.1.2 allows remote attackers to read arbitrary files via backslash sequences (\..). The JSP fails to sanitize path input properly, enabling attackers to escape the web root and access sensitive 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= 2.1.2CVSS 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.
-
Identify if Resin server is installedCheck for Resin installation by looking for Resin-related directories or files. Common locations include /usr/local/resin, /opt/resin, or C:\resin on Windows. Also check for resin processes running on common ports (8080, 80).Affected if Resin server is found running on the system
-
Determine the installed Resin versionCheck the Resin version by examining the resin.jar file or the startup scripts. Look in the Resin lib directory for resin.jar and check its version, or run 'java -jar resin.jar -version' if available. Also check for a version.txt or VERSION file in the Resin installation directory.Affected if The installed version is exactly 2.1.2
-
Locate view_source.jsp in the web rootSearch for view_source.jsp within the web applications deployed on Resin. Common paths include the doc or webapps directory under the Resin installation. Use: find /path/to/resin -name 'view_source.jsp' or dir /s C:\view_source.jsp on Windows.Affected if view_source.jsp exists and is accessible via the web server
-
Test for directory traversal vulnerabilityAttempt to access a known file outside the web root using the backslash sequence. For example, request a URL like: http://yourserver:8080/view_source.jsp?path=..\..\..\windows\system32\config (on Windows) or http://yourserver:8080/view_source.jsp?path=..\..\..\etc\passwd (on Unix). The exact parameter name may vary - check the JSP source for the path parameter.Affected if The server returns contents of files outside the web root directory
A system is affected if Resin version 2.1.2 is installed with view_source.jsp accessible and the path parameter accepts backslash traversal sequences to read 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 from the obsolete Resin 2.1.2 to a current supported version, or remove/disable the vulnerable view_source.jsp if upgrading is not feasible. Apply input validation to path parameters in any remaining traversal-prone code.
- Consultation6.0 h
- Implementation32.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1987 — 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-2002-1987 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