First published: Fri Jun 19 2015(Updated: )
Andrea Palazzo reported the following problem affecting IcedTea-Web: """ Using HTTPUrlConnection it is possible to set custom values for blacklisted headers, even if allowRestrictedHeaders is false, by supplying "Name:value" as name. Also, if needed, trailing ":" could be stripped off using an array as header value. """ Acknowledgement: Red Hat would like to thank Andrea Palazzo of Truel IT for reporting this issue.
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle JDK 6 | =1.6.0-update101 | |
Oracle JDK 6 | =1.7.0-update85 | |
Oracle JDK 6 | =1.8.0-update51 | |
Oracle JDK 6 | =1.8.0-update60 | |
Oracle Java Runtime Environment (JRE) | =1.6.0-update_101 | |
Oracle Java Runtime Environment (JRE) | =1.7.0-update_85 | |
Oracle Java Runtime Environment (JRE) | =1.8.0-update_51 | |
Oracle Java Runtime Environment (JRE) | =1.8.0-update_60 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-4806 is classified as a medium severity vulnerability.
To fix CVE-2015-4806, update your Oracle JDK or JRE to the latest version available from Oracle that addresses this vulnerability.
CVE-2015-4806 affects specific versions of Oracle JDK 6, 7, and 8, as well as the corresponding Oracle JRE versions.
CVE-2015-4806 is a security vulnerability that allows the setting of custom values for blacklisted headers in HTTPUrlConnection.
Yes, CVE-2015-4806 could potentially be exploited for header injection attacks due to improper handling of restricted headers.