| Summary: | OpenSSL Padding Oracle Attack (CVE-2016-2107) | ||
|---|---|---|---|
| Product: | Community | Reporter: | John Arthorne <john.arthorne> |
| Component: | Servers | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P2 | CC: | contact, Silenio_Quarti, steve_northover |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
John Arthorne
Moving to foundation to fix anything at the server level (patching server, etc). Please move back if this has to be done at the application level. Webmaster, can you please comment on whether this is something for you to fix, or if this a configuration/application issue on the orion.eclipse.org vservers? It doesn't look like other eclipse.org properties are affected by the issue so I am assuming it is the latter, but it would be great to get your input. Thanks! We don't provide the SSL certs for project vservers, so this falls on the project team managing the vserver. -M. (In reply to Eclipse Webmaster from comment #3) > We don't provide the SSL certs for project vservers, so this falls on the > project team managing the vserver. > > -M. Thank you Matt for the prompt feedback. In that particular case tho, it looks like orion.eclipse.org is using *.eclipse.org's cert? 15:26 $ openssl s_client -showcerts -connect orion.eclipse.org:443 CONNECTED(00000003) depth=2 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert High Assurance EV Root CA verify return:1 depth=1 C = US, O = DigiCert Inc, OU = www.digicert.com, CN = DigiCert SHA2 High Assurance Server CA verify return:1 depth=0 C = CA, ST = Ontario, L = Ottawa, O = "Eclipse.org Foundation, Inc.", OU = IT, CN = *.eclipse.org verify return:1 --- Certificate chain 0 s:/C=CA/ST=Ontario/L=Ottawa/O=Eclipse.org Foundation, Inc./OU=IT/CN=*.eclipse.org i:/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert SHA2 High Assurance Server CA -----BEGIN CERTIFICATE----- Can you please double check, maybe orion has a slightly different setup than a typical project vserver? Thanks! Ok that's unusual. Since the root issue is probably in the SSL libraries, I've reached out the Orion PLs, as we can just shut this vserver down if it's no longer needed(or being maintained by the project). -M. Ok the OpenSSL libs have been updated, the server rebooted and the test tool now returns: $ go run main.go orion.eclipse.org 2017/09/01 16:26:53 Vulnerable: false Closing as fixed and removing the security flag. -M. |