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 @


From EGIWiki
Jump to navigation Jump to search
Main page Software Security Checklist Issue Handling Advisories Notes On Risk Advisory Template More


** WHITE information - Unlimited distribution allowed                       **  

** see for distribution restrictions **


Title:       EGI SVG Advisory 'Low' RISK - VOMs Potential DoS  [EGI-SVG-2014-7159]

Date:        2015-08-18 



A vulnerability has been found which allows a possible DoS attack on the VOMS server.

This has been fixed by the VOMS team and the fixed version has been released in the EGI UMD.

Note that this was fixed in Feb 2015, but the advisory was missed. 


An error was introduced in VOMS 2.0.11 where there was an attempt to limit the number of concurrent 
connections to the VOMS server. However, this was handled incorrectly and it is possible that a DoS 
attack could take place.  
This is also an operational problem, as the mis-handling means it may not be possible to connect to a 
VOMS server when no attempt at a malicious DoS attack is being made. 

Risk category

This issue has been assessed as 'Low' risk by the EGI SVG Risk Assessment Team 

Affected software

This has been fixed in VOMS 2.0.12-1 which was released in UMD 3.11.0 in Feb 2015 

VOMs Server version voms-2.0.11-1 has been shown to be vulnerable, and it's thought that 
only 2.0.11 is vulnerable.



Component installation information

The official repository for the distribution of grid middleware for EGI sites is 
which contains the EGI Unified Middleware Distribution (UMD).

Sites using the EGI UMD 3 should see:

Sites who wish to install directly from the EMI release should see:


Sites are recommended to update relevant components in due course.


This vulnerability was reported by Robert Frank from the University of Manchester.


2014-06-17 Vulnerability reported by Robert Frank 
2014       Acknowledgement from the EGI SVG to the reporter
2014-06-17 Software providers responded and involved in investigation
2014-06-18 Assessment by the EGI Software Vulnerability Group reported to the software providers
2014-06-18 Found it has already been fixed by the VOMS development team, it was
           considered a more serious operational issue
2014-11-10 Update in EMI repository
2015-02-16 Updated packages available in the EGI UMD
2015-08-17 Noticed that the advisory for this issue had been missed
2015-08-18 Advisory sent to sites
2015-08-18 Public disclosure