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


Title:       EGI SVG 'ALERT' [TLP:WHITE] ZeroMQ Vulnerability [EGI-SVG-CVE-2019-13132] 

Date:        2019-07-10 

Affected software and risk

Vulnerability concerning ZeroMQ

Package : ZeroMQ
CVE ID  : CVE-2019-13132

A vulnerability in ZeroMQ (>=4.0.0) has been announced, where a remote, unauthenticated client may cause a stack 
overflow and overwrite the stack with arbitrary data.  [R 1], [R 2], [R 3]

Actions required/recommended

ZeroMQ is one of the supported messaging solutions in OpenStack. If any cloud site is using ZeroMQ, they should update 
urgently, as should any site using ZeroMQ for any other service. 

Component installation information

For Ubuntu see [R 2]

For Debian see [R 3]

For SUSE see [R 4]


** WHITE information - Unlimited distribution 
   - see for distribution restrictions***                       

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


Comments or questions should be sent to svg-rat  at

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
the EGI Software Vulnerability Group will take a look according to the procedure defined in [R 5]  

Note that this is undergoing revision to fully handle vulnerabilities in the EOSC-hub era. 


[R 1]

[R 2]

[R 3]

[R 4]

[R 5]


SVG was alerted to this vulnerability by Barbara Krasovec

Yyyy-mm-dd  [EGI-SVG-2019-CVE-2019-13132] 

2019-07-09 SVG alerted to this issue by Barbara Krasovec
2019-07-09 Acknowledgement from the EGI SVG to the reporter
2019-07-09 SVG decided to send an alert
2019-07-10 Alert sent to sites


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 5]  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 Software Vulnerability Group

Note that the SVG issue handling procedure is currently under review, to take account of the increasing inhomogeneity 
of the EGI infrastructure and the services in the EOSC-hub catalogue.

On behalf of the EGI SVG,