Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
6.8

IcedTea lets forged Java app signatures run

CVE-2011-0025 · published 15 years ago
Summary

IcedTea versions before the latest updates can fail to properly check the authenticity of Java program files that are only partly signed or signed by more than one source. This weakness could let an attacker make malicious code appear to come from a trusted supplier and have it run on users' computers. Update IcedTea to the newest release to restore correct signature verification.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
redhat icedtea 1.7
1.7.1
1.7.2
1.7.3
1.7.4
1.7.5
1.7.6
1.7.7
1.8
1.8.1
1.8.2
1.8.3
6 more version ranges
cpe:2.3:a:redhat:icedtea:1.7:*:*:*:*:*:*:*
Original advisory text
IcedTea 1.7 before 1.7.8, 1.8 before 1.8.5, and 1.9 before 1.9.5 does not properly verify signatures for JAR files that (1) are "partially signed" or (2) signed by multiple entities, which allows r...
IcedTea 1.7 before 1.7.8, 1.8 before 1.8.5, and 1.9 before 1.9.5 does not properly verify signatures for JAR files that (1) are "partially signed" or (2) signed by multiple entities, which allows remote attackers to trick users into executing code that appears to come from a trusted source.
References
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit (estimated)
  • Gives an attacker partial control (estimated)
Severity
6.8 Medium
Exploitation
3% chance of attack within 30 days
Type
CWE-20Improper Input Validation
Timeline
Published4 Feb 2011
Updated30 Oct 2026
First seen29 Sep 2026
Sources
CVE-2011-0025 · NVD
Track software like this
Free during beta