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] CRITICAL risk Multiple Oracle Database and other Oracle Vulnerabilities 
             CVE-2018-3259, CVE-2018-3299, CVE-2018-7489  [EGI-SVG-CVE-2018-3259] 

Date:        2018-10-18
Updated:     2018-10-23

Affected software and risk

CRITICAL risk vulnerabilities concerning the Oracle Database

Package : Oracle Database
CVE ID  : CVE-2018-3259, CVE-2018-3299, CVE-2018-7489 

Oracle has announced patches for multiple Vulnerabilities [R 1] including two CVE-2018-3259, CVE-2018-3299 
concerning the Oracle Database which may be exploited remotely without authentication. 

**UPDATE 2018-10-23** 

This includes critical vulnerabilities concerning Java 1.7 and higher (Oracle, some also OpenJDK).

Actions required/recommended

Any site running the Oracle Database should update urgently if they have not done so already.
Sites using other Oracle products should also check [R 1] and ensure any relevant patches are applied.

**UPDATE 2018-10-22** 

Services using java-1.7 or higher (either Oracle or OpenJDK) are advised to update and restart services. 

Component installation information

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

For OpenJDK java 1.8 distributed with RedHat 6 and 7 see [R 3], [R 4]

For OpenJDK java distributed with Debian see [R 5], [R 6]

Affected software details

See [R 1], [R 3], [R 4], [R 5], [R 6]


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

[R 3]

[R 4]

[R 5]

[R 6]


SVG was alerted to this vulnerability by David Crooks from STFC who is a member of SVG.

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

2018-10-17 SVG alerted to this issue by David Crooks 
2018-10-18 EGI SVG Risk Assessment completed
2018-10-18 Brief Alert sent to sites
2018-10-23 Update to explicitly include referring to Java 1.8


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,