Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "SVG:Advisory-SVG-CVE-2017-12611"

From EGIWiki
Jump to navigation Jump to search
(Created page with "{{svg-header}} <pre> Title: EGI SVG INFORMATION [TLP:AMBER] Apache Struts vulnerabilities [EGI-SVG-CVE-2017-12611] Date: 2017-09-12 Updated: 2017-10-10 Aff...")
 
 
Line 1: Line 1:
{{svg-header}}
{{svg-header}}
<pre>
<pre>
Title:      EGI SVG INFORMATION [TLP:AMBER] Apache Struts vulnerabilities  [EGI-SVG-CVE-2017-12611]   
Title:      EGI SVG INFORMATION [TLP:WHITE] Apache Struts vulnerabilities  [EGI-SVG-CVE-2017-12611]   


Date:        2017-09-12
Date:        2017-09-12
Line 48: Line 48:
===========
===========


** AMBER information - Limited distribution - see  
** WHITE information - Unlimited distribution - see  
https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions **   
https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions **   



Latest revision as of 18:38, 8 February 2018

Main page Software Security Checklist Issue Handling Advisories Notes On Risk Advisory Template More

Advisory-SVG-CVE-2017-12611

Title:       EGI SVG INFORMATION [TLP:WHITE] Apache Struts vulnerabilities  [EGI-SVG-CVE-2017-12611]  

Date:        2017-09-12
Updated:     2017-10-10


Affected software and risk
==========================

Vulnerabilities concerning Apache Struts have been reported. 

Package : Apache Struts 
CVE ID  : CVE-2017-12611 CVE-2017-9805 

Remote code execution vulnerabilities have been reported in Apache Struts, exploits are available publicly, 
and some sites are already seeing active vulnerability probing for these vulnerabilities. 

SVG has not identified any means where these vulnerabilities are exploitable in EGI at present. 

** UPDATE 2017-10-10 **

Further investigation was carried out, the development teams contacted, and no other usage of Apache Struts was found.


Actions required/recommended
============================

None at present. 


More information
================

2 Remote code execution attacks have been identified [R 1] [R 2]   

VOMS Admin, which uses Struts, has been assessed not vulnerable by the developers.

SVG members are not aware of any other usage in EGI. 

** Update 2017-10-10 **

The developer groups were alerted to this, in case any software is affected, and none reported.


TLP and URL
===========

** WHITE information - Unlimited distribution - see 
https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions **  

URL:   https://wiki.egi.eu/wiki/SVG:Advisory-SVG-CVE-2017-12611 

Minor updates may be made without re-distribution to the sites


Comments
========

Comments or questions should be sent to svg-rat  at  mailman.egi.eu

If you find or become aware of another vulnerability which is relevant to EGI you may 
report it by e-mail to  

report-vulnerability at egi.eu
 
the EGI Software Vulnerability Group will take a look according to the procedure defined in [R 3]  


References
==========

[R 1] https://struts.apache.org/docs/s2-052.html

[R 2] https://struts.apache.org/docs/s2-053.html

[R 3] https://documents.egi.eu/public/ShowDocument?docid=2538

Credit
======

SVG was alerted to this vulnerability by Vincent Brillault 

Timeline  
========
Yyyy-mm-dd  [EGI-SVG-2017-CVE-2017-12611] 

2017-09-06 SVG alerted to this issue by Vincent Brillault
2017-09-06 Acknowledgement from the EGI SVG to the reporter
2017-09-06 Investigation of vulnerability and relevance to EGI carried out for VOMS Admin 
           by Andrea Ceccanti 
2017-09-08 Active vulnerability probing observed by Fyodor Yarochkin
2017-09-11 IRTF meeting agreed a good idea to inform sites
2017-09-12 Sites informed of current status
2017-10-10 No further usage of Apache Structs found, so advisory made public 
           and issue closed.


Context
=======

This advisory has been prepared as part of the effort to fulfil EGI SVG's purpose 
"To minimize the risk to the EGI infrastructure arising from software vulnerabilities"

The risk is that assessed by the group, according to the EGI SVG issue handling 
procedure [R 3]  in the context of how the software is used in the EGI 
infrastructure. It is the opinion of the group, we do not guarantee it to be correct. 

The risk may also be higher or lower in other deployments depending on how the 
software is used.   

Others may re-use this information provided they:-

1) Respect the provided TLP classification

2) Credit the EGI https://www.egi.eu/ Software Vulnerability Group