[
https://issues.apache.org/jira/browse/HADOOP-11217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated HADOOP-11217:
-----------------------------------
Description:
We should disable SSLv3 in KMS to protect against the POODLEbleed vulnerability.
See
[CVE-2014-3566|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3566]
We have {{sslProtocol="TLS"}} set to only allow TLS in ssl-server.xml, but when
I checked, I could still connect with SSLv3. There documentation is somewhat
unclear in the tomcat configs between {{sslProtocol}}, {{sslProtocols}}, and
{{sslEnabledProtocols}} and what each value they take does exactly. From what
I can gather, {{sslProtocol="TLS"}} actually includes SSLv3 and the only way to
fix this is to explicitly list which TLS versions we support.
> Disable SSLv3 (POODLEbleed vulnerability) in KMS
> ------------------------------------------------
>
> Key: HADOOP-11217
> URL: https://issues.apache.org/jira/browse/HADOOP-11217
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
> Affects Versions: 2.6.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Blocker
>
> We should disable SSLv3 in KMS to protect against the POODLEbleed
> vulnerability.
> See
> [CVE-2014-3566|http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3566]
> We have {{sslProtocol="TLS"}} set to only allow TLS in ssl-server.xml, but
> when I checked, I could still connect with SSLv3. There documentation is
> somewhat unclear in the tomcat configs between {{sslProtocol}},
> {{sslProtocols}}, and {{sslEnabledProtocols}} and what each value they take
> does exactly. From what I can gather, {{sslProtocol="TLS"}} actually
> includes SSLv3 and the only way to fix this is to explicitly list which TLS
> versions we support.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
