First published: Mon Aug 24 2015(Updated: )
It was discovered that the IcedTea-Web used codebase attribute of the <applet> tag on the HTML page that hosts Java applet in the Same Origin Policy (SOP) checks. As the specified codebase does not have to match the applet's actual origin, this allowed malicious site to bypass SOP via spoofed codebase value. Note that for Java applets, origin used for SOP checks is the site from which applet was loaded, not the site hosting the page embedding applet: <a href="https://code.google.com/p/browsersec/wiki/Part2#Same-origin_policy_for_Java">https://code.google.com/p/browsersec/wiki/Part2#Same-origin_policy_for_Java</a> Acknowledgement: This issue was discovered by Red Hat Product Security.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
icedtea-web |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-5236 has a medium severity level due to its ability to bypass the Same Origin Policy.
To fix CVE-2015-5236, update IcedTea-Web to the latest version that addresses this vulnerability.
CVE-2015-5236 affects IcedTea-Web across all versions prior to the patches.
Yes, CVE-2015-5236 can allow attackers to execute unauthorized operations on behalf of the user, potentially leading to a security breach.
The implications of CVE-2015-5236 include increased risk of cross-site scripting attacks as the Same Origin Policy is bypassed.