Skip to content
Fencer Intel
medium 5.0

CVE-2011-2513 json

The Java Network Launching Protocol (JNLP) implementation in IcedTea6 1.9.x before 1.9.9 and before 1.8.9, and IcedTea-Web 1.1.x before 1.1…

published 2014-05-14 12 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2498

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

The Java Network Launching Protocol (JNLP) implementation in IcedTea6 1.9.x before 1.9.9 and before 1.8.9, and IcedTea-Web 1.1.x before 1.1.1 and before 1.0.4, allows remote attackers to obtain the username and full path of the home and cache directories by accessing properties of the ClassLoader.

Patch / fix

  • icedtea-web Debian 14, Debian 13, Debian 12 1.1.2-1

debian advisories DEBIAN-CVE-2011-2513

  • icedtea-web RHEL 6 1.0.4-2.el6_1
  • icedtea-web-javadoc RHEL 6 1.0.4-2.el6_1

red hat advisories RHSA-2011:1100

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-2513 updated cvss 4.3

icedtea-web: home directory path disclosure to untrusted applications

  • Red Hat Enterprise Linux Server (v. 6) icedtea-web 1.0.4-2.el6_1 Red Hat Enterprise Linux Server Optional (v. 6) icedtea-web 1.0.4-2.el6_1, icedtea-web-javadoc 1.0.4-2.el6_1
    fixed: vendor fix RHSA-2011:1100
  • Red Hat Enterprise Linux 5 java-1.6.0-openjdk Red Hat Enterprise Linux 6 java-1.6.0-openjdk, java-1.6.0-openjdk-src, java-1.6.0-openjdk-demo, java-1.6.0-openjdk-javadoc
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.50% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.