CVE-2002-0058
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 · uneditedVulnerability in Java Runtime Environment (JRE) allows remote malicious web sites to hijack or sniff a web client's sessions, when an HTTP proxy is being used, via a Java applet that redirects the session to another server, as seen in (1) Netscape 6.0 through 6.1 and 4.79 and earlier, (2) Microsoft VM build 3802 and earlier as used in Internet Explorer 4.x and 5.x, and possibly other implementations that use vulnerable versions of SDK or JDK.
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 confidenceA vulnerability in Java Runtime Environment allows malicious applets to hijack or sniff web client sessions when an HTTP proxy is configured. The applet can redirect the session to an attacker-controlled server, enabling session theft or traffic sniffing. Affects Netscape 6.0-6.1, 4.79 and earlier, Microsoft VM build 3802 and earlier (IE 4.x/5.x), and similar vulnerable JDK/SDK implementations.
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= 3802= 1.1.8= 1.1.8= 1.2.2= 1.3.0= 1.1.8_007= 1.2.2_10= 1.2.2_010= 1.3_02CVSS 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 installed Java Runtime Environment versionCheck the JRE/JDK version by running 'java -version' or viewing the Java control panel/About section in affected browsers (IE 4.x/5.x with Microsoft VM, or Netscape 6.0-6.1/4.79). Compare the version number to the affected list: Microsoft VM build 3802 or earlier; Sun Jdk 1.1.8; Sun Jre 1.1.8, 1.2.2, 1.3.0; Sun Sdk 1.1.8_007, 1.2.2_10, 1.2.2_010, 1.3_02.Affected if The installed Java version matches one of the affected versions listed above.
-
Determine if HTTP proxy is configuredCheck browser or system proxy settings. In Internet Explorer, go to Tools > Internet Options > Connections > LAN Settings. In Netscape, check Edit > Preferences > Advanced > Proxies. Look for configured proxy server addresses or automatic configuration scripts.Affected if An HTTP proxy server is explicitly configured in the browser or system settings.
-
Verify Java applet execution is enabledCheck browser security settings for Java applet permissions. In IE, verify ActiveX and Java settings under Tools > Internet Options > Security > Custom Level. In Netscape, check Edit > Preferences > Advanced > Java. Look for settings that allow Java applets to run.Affected if Java applets are permitted to execute in the browser security configuration.
The environment is affected only if an affected Java VM version (as listed) is installed AND an HTTP proxy is configured AND Java applets are enabled in the browser; otherwise, the exploit conditions are not met.
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 dataDisable Java applets in affected browsers, or upgrade to patched JRE versions. Since this affects 2002-era browsers and VMs which are obsolete, modern systems are not vulnerable.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0058 — 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-0058 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