CVE-2002-0665
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 · uneditedMacromedia JRun Administration Server allows remote attackers to bypass authentication on the login form via an extra slash (/) in the 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 confidenceMacromedia JRun Administration Server contains an authentication bypass vulnerability where remote attackers can bypass the login form authentication mechanism by appending an extra slash (/) to the URL. This path manipulation allows unauthenticated access to administrative functions.
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= 3.0= 3.1= 4.0CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 JRun installation and versionLocate JRun installation directory and check version information in release notes, version.properties, or About dialog in admin console. Common installation paths: C:\JRun (Windows) or /opt/jrun (Unix/Linux)Affected if Installed version matches 3.0, 3.1, or 4.0
-
Confirm Administration Server is runningCheck if JRun admin service is listening on its default port (8000-8002 range commonly). Use netstat or equivalent: netstat -an | findstr '8000'Affected if Administration Server process is active and bound to a network interface
-
Verify admin interface is network-accessibleDetermine if the JRun admin URL (such as /admin/ or /jms/) is reachable from network locations, not just localhost. Check firewall rules and server binding configurationAffected if Admin console is bound to 0.0.0.0 or accessible beyond localhost loopback
-
Test URL manipulation for authentication bypassAttempt to access admin functions by appending extra slash to admin URLs, for example: http://server:port/admin/ or http://server:port/jms/ with an additional trailing slash. Observe if authentication is bypassedAffected if Appending extra slash grants access without presenting login credentials
Environment is affected if JRun versions 3.0, 3.1, or 4.0 are installed with the Administration Server exposed to the network and vulnerable to slash-append bypass.
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 dataSince JRun is end-of-life software, the primary remediation is to migrate away from JRun to a supported application server. If continued use is absolutely required, research historical patches from Macromedia/Adobe, though no modern support exists.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0665 — 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-0665 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