JdkApplication · Sun

CVE-2007-3922

MEDIUM · 6.8 CVSS v2.0 Published 2007-07-21

Fix available

A fix is available. Upgrade to after 1.6.0 or later.

See remediation →

77/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Unspecified vulnerability in the Java Runtime Environment (JRE) Applet Class Loader in Sun JDK and JRE 5.0 Update 11 and earlier, 6 through 6 Update 1, and SDK and JRE 1.4.2_14 and earlier, allows remote attackers to violate the security model for an applet's outbound connections by connecting to certain localhost services running on the machine that loaded the applet.

Technical summary

dbcve analysis · high confidence

This is a flaw in the JRE Applet Class Loader that allows malicious applets to bypass the applet sandbox security restrictions and connect to localhost services running on the user's machine. Normally, applets are restricted to only making network connections to the host they were loaded from, but this vulnerability enables them to reach local services, potentially facilitating attacks against local infrastructure or exposing sensitive local data.

MitigationUpdate Java to a version beyond the affected releases (JDK/JRE 5.0 Update 12+, 6 Update 2+, or 1.4.2_15+). As a compensating control, disable Java browser plug-ins or use click-to-play settings to prevent untrusted applets from executing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

JdkApplication

Affected:<= 1.5.0<= 1.6.0

JreApplication

Affected:<= 1.5.0<= 1.6.0

SdkApplication

Affected:<= 1.4.2_14

CVSS breakdown

From the vector

Attack vector: Network
Complexity: M
Authentication: None
Confidentiality: Partial
Integrity: Partial
Availability: Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

Am I affected?

dbcve checks

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

Check installed Java version

Run 'java -version' from command line to obtain the JRE/JDK version string

Affected if Version shows 1.4.2_x where x is 14 or lower, OR 1.5.0_x where x is 12 or lower, OR 1.6.0_x where x is 2 or lower, indicating the installed version falls within the affected ranges (JDK/JRE <=1.4.2_14, <=1.5.0, <=1.6.0)
Identify Java browser plugin presence

Check common browser plugin locations: on Windows check C:\Program Files\Java\jre*\bin\np*.dll or on Unix check ~/.mozilla/plugins/ for libnp*.so files; alternatively, in Firefox navigate to about:plugins and look for Java Applet Plug-in

Affected if A Java Applet Plug-in is listed in the browser plugins, indicating the Java browser integration is installed and could execute malicious applets
Verify applet execution capability

If Java is installed, attempt to verify the plugin status by checking browser settings or the Java Control Panel (Java Plug-in tab) to see if the browser plugin is enabled

Affected if The Java browser plugin is enabled or set to allow applets to run in browsers, meaning the vulnerability can be triggered by visiting a malicious webpage with an embedded applet

A user is affected if their environment has a Java version in the affected ranges (1.4.2_14 and below, 1.5.0 up to update 12, or 1.6.0 up to update 2) AND the Java browser plugin is installed and enabled, allowing untrusted applets to execute and potentially reach localhost services.

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

Remediation

From vendor data

Upgrade available Upgrade to a release after 1.6.0

Interim mitigation

Update Java to a version beyond the affected releases (JDK/JRE 5.0 Update 12+, 6 Update 2+, or 1.4.2_15+). As a compensating control, disable Java browser plug-ins or use click-to-play settings to prevent untrusted applets from executing.

Fix this in Jdk Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing3.0 h
Review / QA1.0 h

10.0 hours of engineering $1,750

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2007-3922 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2007-3922?

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.

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

At a glance

A fix existsUpgrade to after 1.6.0 or later

Severity 6.8 Medium

Exploit likelihood EPSS, next 30 days 2.9%

Affects: Jdk

Remediation

A high-priority fix

Fix this in Jdk 10 hrs · Moderate

Typical engagement from $1,750

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2007-3922 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References