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


Title:       EGI SVG 'ALERT' [TLP:WHITE] CRITICAL risk Oracle Database Vulnerability  [EGI-SVG-CVE-2018-3110] 

Date:        2018-08-17

Affected software and risk

CRITICAL risk vulnerability concerning the Oracle Database

Package : Oracle
CVE ID  : CVE-2018-3110

Oracle has announced a Vulnerability [R 1] with a CVSS v3 base score of 9.9  which can result in 
complete compromise of the Oracle Database and shell access to the underlying server. 

Actions required/recommended

Any site running the Oracle Database should update urgently if they have not done so already.

Affected software details

See [R 1] 

Component installation information

See information from oracle - e.g. [R 1] 


** 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 2]  

Note that this has been updated and the latest version approved by the Operations Management Board in November 2017


[R 1]

[R 2]


SVG was alerted to this vulnerability by Darren Moore at STFC

Yyyy-mm-dd  [EGI-SVG-CVE-2018-3110] 

2018-08-16 SVG alerted to this issue by Darren Moore at STFC
2018-08-16 Acknowledgement from the EGI SVG to the reporter
2018-08-17 Brief 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 2]  
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

On behalf of the EGI SVG,