CVE-2011-3546
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 · uneditedUnspecified vulnerability in the Java Runtime Environment component in Oracle Java SE JDK and JRE 7, 6 Update 27 and earlier, and JavaFX 2.0 allows remote untrusted Java Web Start applications and untrusted Java applets to affect confidentiality and integrity via unknown vectors related to Deployment.
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 · moderate confidenceVulnerability in the Java Runtime Environment Deployment component allows remote untrusted Java Web Start applications and untrusted Java applets to affect confidentiality and integrity via unknown vectors. The flaw affects Java SE 7, 6 Update 27 and earlier, and JavaFX 2.0.
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.0= 1.7.0<= 1.6.0= 1.6.0= 1.7.0<= 1.6.0= 1.6.0= 1.6.0= 1.6.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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/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.
-
Check installed JRE/JDK versionRun 'java -version' from command line and note the version string. For JDK, also run 'javac -version'. Look for versions like 1.6.0, 1.6.0_u27 or earlier, or 1.7.0 any update.Affected if Version output shows 1.7.0 (any update), 1.6.0, or 1.6.0_u27 or earlier, indicating an unpatched vulnerable release.
-
Check Java Web Start availabilityRun 'javaws -version' or locate javaws executable on the system. On Windows, check Program Files/Java folder for javaws.exe.Affected if Java Web Start (javaws) is installed and present on the system.
-
Check Java browser pluginExamine browser plugin directories: Windows: C:\Program Files\Java\jre6\bin\plugin2\ (or similar path). On Linux: check ~/.mozilla/plugins/ for libnpjp2.so. On Mac: check /Library/Internet Plug-Ins/JavaAppletPlugin.plugin.Affected if Java browser plugin (npjp2.dll or libnpjp2.so) exists in browser plugin directories.
-
Identify Java deployment configurationOn Windows, check Control Panel > Java > Security tab or examine java deployment.properties file at %APPDATA%\Oracle\Java\Deploy\deployment.properties.Affected if Java deployment is configured and enabled, allowing untrusted applets or Java Web Start applications to run.
User is affected if their installed Java version is 1.7.0 any update, 1.6.0 any update through u27, or 1.6.0 and earlier, AND Java Web Start or browser plugin components are present and enabled on the system.
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 dataUpdate Java to a patched version (later than the affected releases) or disable Java plugin in browsers and restrict Java Web Start execution to trusted sources.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3546 — 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-2011-3546 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