Icedtea WebApplication · Redhat

CVE-2013-1926

MEDIUM · 5.8 CVSS v2.0 Published 2013-04-29

Fix available

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

See remediation →

67/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The IcedTea-Web plugin before 1.2.3 and 1.3.x before 1.3.2 uses the same class loader for applets with the same codebase path but from different domains, which allows remote attackers to obtain sensitive information or possibly alter other applets via a crafted applet.

Technical summary

dbcve analysis · high confidence

The IcedTea-Web plugin fails to properly isolate class loaders for Java applets. When applets from different domains share the same codebase path, the plugin incorrectly reuses the same class loader, allowing a malicious applet from one domain to access or manipulate classes and resources from applets running in a different domain.

MitigationUpgrade IcedTea-Web to version 1.2.3, 1.3.2, or later, which implements proper class loader isolation based on domain origin.

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

Icedtea WebApplication

Affected:<= 1.2.2= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.1= 1.1.1= 1.1.2= 1.1.3

Ubuntu LinuxOperating system

Affected:= 10.04= 11.10= 12.04= 12.10

OpensuseOperating system

Affected:= 12.2

CVSS breakdown

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?

dbcve checks

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

Confirm IcedTea-Web is installed

Check for the presence of the IcedTea-Web plugin or package. On Debian/Ubuntu systems: dpkg -l | grep -i icedtea. On RPM-based systems (Red Hat/openSUSE): rpm -qa | grep -i icedtea. Also check for the npapijava or libjavaplugin.so browser plugin in common plugin directories.

Affected if No IcedTea-Web package or plugin is found on the system, the system is not affected by this CVE.
Determine the installed IcedTea-Web version

Run the version command for the installed package. On Debian/Ubuntu: dpkg -l <package_name> | grep icedtea. On RPM-based systems: rpm -q --qf '%{VERSION}-%{RELEASE}' <package_name>. Compare the version number against the affected range: versions 1.0 through 1.2.2, and 1.0.x, 1.1.x series.

Affected if The installed version is 1.2.2 or lower, or falls in the 1.0.x, 1.1.x, 1.1.1 through 1.1.3 series, the system is potentially affected.
Verify Java plugin is enabled in browsers

Check browser plugin configuration. Look for the IcedTea-Web plugin (npapijava.so or javaplugin) in browser plugin directories (typically ~/.mozilla/plugins, /usr/lib/mozilla/plugins, or /usr/lib/browser-plugins). Check if the plugin is symlinked or registered in the browser.

Affected if The IcedTea-Web Java plugin is enabled and loaded by a browser, the class loader isolation flaw can be triggered when running applets.
Identify if applets from multiple domains share codebase

Review the Java applet deployment descriptors (JNLP files) or HTML embed tags in use. The vulnerability specifically manifests when applets from different domains share the same codebase path.

Affected if Multiple applets from different domains are configured to use identical codebase paths, the class loader reuse vulnerability can be exploited.

A system is affected if it runs a vulnerable IcedTea-Web version (1.0 through 1.2.2, or 1.x series up to 1.1.3) with the Java browser plugin enabled and uses or could use Java applets from different domains sharing the same codebase.

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

Remediation

From vendor data

Upgrade available Upgrade to a release after 1.2.2

Interim mitigation

Upgrade IcedTea-Web to version 1.2.3, 1.3.2, or later, which implements proper class loader isolation based on domain origin.

Fix this in Icedtea Web Scoped from the published advisory

Consultation4.0 h
Implementation2.0 h
Testing6.0 h
Review / QA3.0 h

15.0 hours of engineering $2,600

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2013-1926 — 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-2013-1926 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2013-1926?

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.2.2 or later

Severity 5.8 Medium

Exploit likelihood EPSS, next 30 days 1.9%

Affects: Icedtea Web

Remediation

Need this fixed?

Fix this in Icedtea Web 15 hrs · Moderate

Typical engagement from $2,600

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2013-1926 and return a fixed quote.

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