EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #08530

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] EPrints Security Announcement - February 2020

Hi all,

EPrints Services was recently made aware of a small number of security vulnerabilities within the EPrints codebase, affecting both EPrints 3.4 and EPrints 3.3.
I have created two patch files to fix the vulnerabilities and uploaded them to files.eprints.org.

- EPrints 3.4.2 : https://files.eprints.org/2548/
- EPrints 3.3.x : https://files.eprints.org/2549/

The former fixes the EPrints 3.4.2 release and the latter fixes EPrints 3.3 (based on the current HEAD of https://github.com/eprints/eprints). These links also provide instructions on how to apply the patch file and some more details on the affected files.  There are references to the Common Vulnerabilities and Exposure (CVE) IDs but as of now these are yet to be published.  All the vulnerabilities identified relate to either Cross-Site Scripting (XSS) or Remote Code Execution (RCE) vulnerabilities.  All of these vulnerabilities would require analysis of the codebase to determine an exploit.  It is very unlikely that generic tools used to identify vulnerabilities would discover these, as specific knowledge is required.

I have also updated to patch these vulnerabilities on both the eprints and eprints3.4 GitHub repositories for the eprints organisation (https://github.com/eprints).  The next release of EPrints 3.4 (3.4.3) will have these security fixes in place.

EPrints Services customers both those who EPrints Services host and those that self-host have either been patched or where this has not been possible, informed of the vulnerabilities and how they can be fixed.

If you have any follow-up questions please feel free to ask. Hopefully, the CVEs will be published shortly for those interested in more detail.  However, they were raised by a third party, who I have only just given go-ahead to make these public.

Regards

David Newman

Virus-free. www.avg.com