Page History
...
Info | ||
---|---|---|
| ||
This documentation was produced with Confluence software. A PDF version was generated directly from Confluence. An online, updated version of this 5.x Documentation is also available at: https://wiki.duraspace.org/display/DSDOC5x |
Warning |
---|
Support for DSpace 5 will be ending on January 1, 2023. See Support for DSpace 5 and 6 is ending in 2023 |
Welcome to Release 5.311, a bug-fix release for the DSpace 5.x platform. For information on upgrading to DSpace 5, please see Upgrading DSpace.
Table of Contents |
---|
5.
...
11 Release Notes
Note | ||
---|---|---|
|
...
| |
DSpace 5.11 contains security and bug fixes for both the JSPUI and XMLUI. To ensure your 5.x site is secure, we highly recommend ALL DSpace 5.x users upgrade to DSpace 5.11. DSpace 5.11 upgrade instructions are available at: Upgrading DSpace |
Summary
DSpace 5.11 is a bug fix release to resolve several issues located in previous 5.x releases. As it only provides only security and bug fixes, DSpace 5.11 should constitute an easy upgrade from DSpace 5.x for most users. No database changes should be necessary when upgrading from DSpace 5.x to 5.11.
Security fixes include:
- [HIGH] CVE-2022-31195 (impacts XMLUI and JSPUI) : Path traversal vulnerability in Simple Archive Format package import (ItemImportService API). This means a malicious SAF (simple archive format) package could cause a file/directory to be created anywhere the Tomcat/DSpace user can write to on the server. This path traversal is only possible by a user with special privileges (Administrators or someone with command-line access to the server).
- Reported by Johannes Moritz of Ripstech
- [HIGH] CVE-2022-31194 (impacts JSPUI only) : The JSPUI resumable upload implementations in SubmissionController and FileUploadRequest are vulnerable to multiple path traversal attacks, allowing an attacker to create files/directories anywhere on the server writable by the Tomcat/DSpace user, just by modifying some request parameters during submission. This path traversal can only be executed by a user with submitter rights.
- Reported by Johannes Moritz of Ripstech
- [HIGH] CVE-2022-31193 (impacts JSPUI only) : The JSPUI controlled vocabulary servlet is vulnerable to an open redirect attack, where an attacker can craft a malicious URL that looks like a legitimate DSpace/repository URL. When that URL is clicked by the target, it redirects them to a site of the attacker's choice.
- Reported by Johannes Moritz of Ripstech
- [MODERATE] CVE-2022-31191 (impacts JSPUI only) : The JSPUI spellcheck "Did you mean" HTML escapes the data-spell attribute in the link, but not the actual displayed text. Similarly, the JSPUI autocomplete HTML does not properly escape text passed to it. Both are vulnerable to Cross Site Scripting (XSS).
- Reported by Hassan Bhuiyan, Brunel University London
- [MODERATE] CVE-2022-31192 (impacts JSPUI) : The JSPUI "Request a Copy" feature is vulnerable to Cross Site Scripting (XSS) attacks.
- Reported by Andrea Bollini of 4Science
Major bug fixes include:
- Fix Mirage 2 build broken by disappearance of JRuby gems torquebox.org mirror: https://github.com/DSpace/DSpace/commit/0428da8dab7a02c592ec96ab9cea545f5b6de42d
- Database fixes
- Migrate
update-sequences.sql
script todspace database
command: DS-4167 (#2361)
- Migrate
- XMLUI fixes
- Fix Discovery label for metadata values under authority control: DS-2852 (#1701)
- Fix missing date values while faceting: DS-3791 (#2679)
- Fix support for custom
sitemap.xmap
in Mirage 2: DS-3545 (#1691)
- JSPUI fixes
- Fix bug in JSPUI Shibboleth session renewal: DS-3444 (#2566)
- Update Sherpa Romeo layout:DS-4377 (#2565)
- Fix issue with duplicate headers when bitstream title has a comma: DS-4340 (#2514)
- REST API fixes:
- Fix Maven build issue due to blocking of plaintext HTTP repositories: #3247 (see #3274)
- Improve performance of collections endpoints: DS-4342 (#2517)
Minor improvements include:
- Fix Discovery index command when using the "-c" (clean) option: DS-4393 (#2605)
- Avoid crosswalking invalid publish dates for Google Scholar: DS-4104 (#2295)
View the full list of changes for DSpace 5.11 on GitHub.
5.11 Acknowledgments
The 5.11 release was led by Alan Orth, Kim Shepherd, Nicholas Woodward and Hrafn Malmquist (of Cottage Labs)
The following individuals provided tests, code or bug fixes or review to the 5.11 release (in alphabetical order by given name): Andrea Bollini, Andrea Jenis Saroni, Andrew Bennet, Bram Luyten, Hrafn Malmquist, Iordanis Kostelidis, Jonas Van Goolen, Kim Shepherd, Kristof De Langhe, Lotte Hofstede, Luigi Andrea Pascarelli, Mark H. Wood, Pascal-Nicolas Becker, Philip Vissenaekens, samuel, Terry Brady, Tim Donohue.
5.10 Release Notes
Note | ||
---|---|---|
| ||
Unfortunately, bug fixes in the DSpace 5.9 release resulted in issues running DSpace 5.9 on Java 7, and with running the REST API and RDF interfaces. These issues are being resolved in an upcoming 5.10 release (see below for more details). Sites which are dependent on one of these features should consider upgrading directly from DSpace 5.8 to 5.10. |
Summary
DSpace 5.10 is a bug fix release to resolve JAR dependency issues found in DSpace 5.9 for users running Java 7 (regardless of Tomcat version).
This release also addresses a bug in the DSpace 5.9 release that prevented VIEW statistics from being logged by DSpace.
Other minor bug fixes have been included in the release.
Major bug fixes include
- DS-4000: DSpace 5.9 - REST Service Does Not Run
- DS-3938: After upgrading PostgreSQL JDBC driver, DSpace does not run on JDK 7
- DS-4020: DSpace 5.9 is not saving VIEW events to statistics repo (SEARCH and WORKFLOW are saved)
Other fixes include
- DS-4007: PDF Text Extractor can cause strings like "content-type" to show up in search snippets
To fully realize the benefit of this fix, a full discover reindex is recommended.
- If you don't reindex, newly added bitstreams would no longer display the file metadata in their index. (But, old bitstreams would still continue to display file metadata until you do a full reindex).
- Institutions unaffected/unconcerned by this bug do not need to reindex. If you do choose to reindex, then the bug would be fully fixed
- DS-2948: Filter-media-> file metadata indexed in full text
- DS-3664: Color Profile Detection Method in ImageMagick filter is prohibitively slow
In addition, this release fixes a variety of minor bugs in the 5.x releases. For more information, see the Changes section below.
Upgrade Instructions
For upgrade instructions from ANY PRIOR VERSION to 5.10, please see Upgrading DSpace
- When upgrading from any 5.x version, if you're reusing your 5.x configuration, make sure to change all instances of Filter attribute "red" to "ref" (e.g. <Filter red="exampleFilter" /> to <Filter ref="exampleFilter" />) in [dspace]/config/crosswalks/oai/xoai.xml. "red" was a temporary workaround for a bug (xoai issue #32), which was first fixed in DSpace 5.4.
No new features in DSpace 5.10
Note |
---|
5.10 is a bug-fix release. This means it includes no new features and only includes the above listed fixes. For a list of all new 5.x Features, please visit the 5.x Release Notes. |
5.10 Acknowledgments
The 5.10 release was led by Terrence W Brady.
The following individuals provided code or bug fixes to the 5.10 release: Terrence W Brady , Alexander Sulfrian , Philip Vissenaekens (Atmire) , Jozsef Marton.
5.9 Release Notes
Note | ||
---|---|---|
| ||
DSpace 5.9 contains security fixes for the JSPUI (only). To ensure your 5.x JSPUI site is secure, we highly recommend ALL JSPUI DSpace 4.x users upgrade to DSpace 5.9. DSpace 5.x XMLUI users may also wish to upgrade as several major bugs have been fixed in the XMLUI as well. DSpace 5.9 upgrade instructions are available at: Upgrading DSpace |
DSpace 5.9 is a security & bug fix release to resolve several issues located in previous 5.x releases. As it only provides bug/security fixes, DSpace 5.9 should constitute an easy upgrade from DSpace 5.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 5.x to 5.9.
JSPUI security fixes include
[HIGH SEVERITY] A user can inject malicious Javascript into the names of EPeople or Groups. This is most severe in sites which allow anyone to register for a new account. (https://jira.duraspace.org/browse/DS-3866 - requires a JIRA account to access.)
Reported by Julio Brafman
[MEDIUM SEVERITY] Any user was able to export metadata to CSV format if they knew the correct JSPUI path/parameters. Additionally, the exported CSV included metadata fields which are flagged as hidden in configuration. (https://jira.duraspace.org/browse/DS-3840 - requires a JIRA account to access.)
Reported by Eike Kleiner (ZHAW, Zurich University of Applied Sciences)
Major bug fixes include
- Update DSpace ORCID Integration to use ORCID API v2 (instead of now obsolete ORCID v1): DS-3447
- Update DSpace Statistics to use GeoIP API v2 (instead of now discontinued GeoIP API v1): DS-3832
- Other API-level fixes (affecting all UIs)
- PostgreSQL JDBC driver upgraded to latest version (to allow for full compatibility with PostgreSQL v10): DS-3854
- Ensure ImageMagick thumbnails respect the orientation of original file: DS-3839
- OAI-PMH Fixes
- XMLUI Fixes
- Fixed Mirage v2 build issues caused by Bower Registry URL change: DS-3936
- Fixed performance issues for Items with 100+ bitstreams: DS-3883
- Fix issue where search results lose Community/Collection context when sorting: DS-3835
- Update Mirage to use recommended MathJax inline delimiters (DS-3087) and to use new CDN location (DS-3560)
In addition, this release fixes minor bugs in the 5.x releases. For more information, see the Changes in 5.x page.
5.9 Acknowledgments
The 5.9 release was led by the DSpace Committers.
The following individuals provided code or bug fixes to the 5.9 release: Pascal-Nicolas Becker, Ben Bosman, Terry Brady, Tim Donohue, Alex Magaz Graça, Lotte Hofstede, Ivan Masár, Hardy Pottinger, Kim Shepherd, Jonas Van Goolen and Mark H. Wood.
5.8 Release Notes
Note | ||
---|---|---|
| ||
DSpace 5.8 contains a fix to the ImageMagick thumbnail creation process. We highly recommend ALL DSpace 5.x users upgrade to DSpace 5.8. DSpace 5.8 upgrade instructions are available at: Upgrading DSpace |
DSpace 5.8 contains a fix for a bug introduced in DSpace 5.7. As it only provides bug fixes, DSpace 5.8 should constitute an easy upgrade from DSpace 5.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 5.x to 5.8.
Major bug fixes include:
- Resolve a performance issue in the ImageMagick Thumbnail Creation process for PDF files (DS-3661)
Other fixes
- Update automated testing resources (DS-3674)
- Set a particular version for CSS processing in Mirage2
5.8 Acknowledgments
The 5.8 release was led by the DSpace Committers.
The following individuals provided code or bug fixes to the 5.8 release: Terry Brady (terrywbrady), Tim Donohue (tdonohue), Hardy Pottinger (hardyoyo). Release support provided by Mark Wood (mwood).
5.7 Release Notes
Note | ||
---|---|---|
| ||
DSpace 5.7 contains security fixes for the XMLUI and JSPUI and REST. To ensure your 5.x site is secure, we highly recommend ALL DSpace 5.x users upgrade to DSpace 5.7. DSpace 5.7 upgrade instructions are available at: Upgrading DSpace |
DSpace 5.7 is a security & bug fix release to resolve several issues located in previous 5.x releases. As it only provides bug/security fixes, DSpace 5.7 should constitute an easy upgrade from DSpace 5.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 5.x to 5.7.
Major bug fixes include:
Security fixes for both JSPUI and XMLUI:
- [HIGH SEVERITY] Basic (Traditional) Workflow approval process is vulnerable to unauthorized manipulations.(https://jira.duraspace.org/browse/DS-3647 - requires a JIRA account to access.)
- Discovered by Pascal Becker (The Library Code / TU Berlin).
- [LOW SEVERITY] DSpace shipped with a version of Apache Commons Configuration that was vulnerable to COLLECTIONS-580 (Deserialization Vulnerability). (https://jira.duraspace.org/browse/DS-3520 - requires a JIRA account to access.)
- Discovered by Alan Orth.
- [HIGH SEVERITY] Basic (Traditional) Workflow approval process is vulnerable to unauthorized manipulations.(https://jira.duraspace.org/browse/DS-3647 - requires a JIRA account to access.)
- Security fixes for REST API:
- [HIGH SEVERITY] A user with submit permissions can bypass workflow approvals by depositing via REST API.(https://jira.duraspace.org/browse/DS-3281 - requires a JIRA account to access.)
- Discovered by Emilio Lorenzo.
- [HIGH SEVERITY] A user with submit permissions can bypass workflow approvals by depositing via REST API.(https://jira.duraspace.org/browse/DS-3281 - requires a JIRA account to access.)
- XMLUI bug fixes:
- JSPUI bug fixes
- READ access rights not being respected on Collection homepage: DS-3441
- Solr Statistics fixes:
- AIP Backup and Restore fixes:
- Failed AIP imports left files in assetstore: DS-2227
5.7 Acknowledgments
The 5.7 release was led by the DSpace Committers.
The following individuals provided code or bug fixes to the 5.7 release: Pascal-Nicolas Becker (pnbecker), Andrea Bollini (abollini), Terry Brady (terrywbrady), Samuel Cambien (samuelcambien), Yana De Pauw, Tom Desair (tomdesair), Peter Dietz (peterdietz), Tim Donohue (tdonohue), Claudia Juergen (cjuergen), Bram Luyten (bram-atmire), Ivan Masar (helix84), Alan Orth (alanorth), Andrea Pascarelli (lap82), Kim Shepherd (kshepherd), Mark Wood (mwoodiupui), Jonas Van Goolen (jonas-atmire), Philip Vissenaekens (PhilipVis), and Arvo Consultores y Tecnología. S.L (arvoConsultores)
5.6 Release Notes
Note | ||
---|---|---|
| ||
DSpace 5.6 contains security fixes for the XMLUI and JSPUI and REST. To ensure your 5.x site is secure, we highly recommend ALL DSpace 5.x users upgrade to DSpace 5.6. DSpace 5.6 upgrade instructions are available at: Upgrading DSpace |
DSpace 5.6 is a security & bug fix release to resolve several issues located in previous 5.x releases. As it only provides bug/security fixes, DSpace 5.6 should constitute an easy upgrade from DSpace 5.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 5.x to 5.6.
Major bug fixes include:
- JSPUI, XMLUI, REST security fixes:
- JSPUI and XMLUI
- [MEDIUM SEVERITY] XML External Entity (XXE) vulnerability in pdfbox. (DS-3309 - requires a JIRA account to access)
- Reported by Seth Robbins
- [MEDIUM SEVERITY] XML External Entity (XXE) vulnerability in pdfbox. (DS-3309 - requires a JIRA account to access)
- JSPUI, XMLUI and REST
- [MEDIUM SEVERITY] Bitstreams of embargoed and/or withdrawn items can be accessed by anyone. (DS-3097 - requires a JIRA account to access)
- Reported by Franziska Ackermann
- Reported by Franziska Ackermann
- [MEDIUM SEVERITY] Bitstreams of embargoed and/or withdrawn items can be accessed by anyone. (DS-3097 - requires a JIRA account to access)
- JSPUI and XMLUI
- JSPUI security fix:
- [HIGH SEVERITY] Any registered user can modify inprogress submission. (DS-2895 - requires a JIRA account to access)
- Reported by Andrea Bollini (4Science)
- Reported by Andrea Bollini (4Science)
- [HIGH SEVERITY] Any registered user can modify inprogress submission. (DS-2895 - requires a JIRA account to access)
- REST security fix:
- [HIGH SEVERITY] SQL Injection Vulnerability in 5.x REST API (DS-3250 - requires a JIRA account to access)
- Reported by Bram Luyten (Atmire)
- [HIGH SEVERITY] SQL Injection Vulnerability in 5.x REST API (DS-3250 - requires a JIRA account to access)
- JSPUI bug fixes:
- XMLUI bug fixes:
- XMLUI: Recyclable Cocoon components should clear local variables (DS-3246)
- XMLUI: "Request a copy" feature was not working when the property request.item-type was set to all ( DS-3294)
- XMLUI: Bug fix to policy search form (DS-3206)
- XMLUI: Recyclable Cocoon components should clear local variables (DS-3246)
- Other minor fixes and improvements
In addition, this release fixes minor bugs in the 5.x releases. For more information, see the Changes in 5.x page.
5.6 Acknowledgments
The 5.6 release was led by Andrea Pascarelli (4Science) and the Committers.
The following individuals provided code or bug fixes to the 5.6 release: Andrea Bollini (abollini), Tim Donohue (tdonohue), Claudia Juergen (cjuergen), Bram Luyten (bram-atmire), Ivan Masar (helix84), oooriii, Andrea Pascarelli (lap82), Hardy Pottinger (hardyoyo), Roeland Dillen (rradillen), Andrea Schweer (aschweer), William Tantzen (wilee53), Mark Wood (mwoodiupui), Bruno Nocera Zanette
5.5 Release Notes
Note | ||
---|---|---|
| ||
DSpace 5.5 contains security fixes for the XMLUI and JSPUI. To ensure your 5.x site is secure, we highly recommend ALL DSpace 5.x users upgrade to DSpace 5.5. DSpace 5.5 upgrade instructions are available at: Upgrading DSpace |
DSpace 5.5 is a security & bug fix release to resolve several issues located in previous 5.x releases. As it only provides bug/security fixes, DSpace 5.5 should constitute an easy upgrade from DSpace 5.x for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 5.x to 5.5.
Major bug fixes include:
- XMLUI security fixes:
- [HIGH SEVERITY] The XMLUI "themes/" path is vulnerable to a full directory traversal. (DS-3094 - requires a JIRA account to access.) This means that ANY files on your system which are readable to the Tomcat user account may be publicly accessed via your DSpace website.
- Reported by Virginia Tech
- Reported by Virginia Tech
- [HIGH SEVERITY] The XMLUI "themes/" path is vulnerable to a full directory traversal. (DS-3094 - requires a JIRA account to access.) This means that ANY files on your system which are readable to the Tomcat user account may be publicly accessed via your DSpace website.
- JSPUI security fixes:
- [MEDIUM SEVERITY] The JSPUI "Edit News" feature (accessible to Administrators) can be used to view/edit ANY files which are readable to the Tomcat user account (DS-3063 - requires a JIRA account to access.)
- Reported by CINECA
- Reported by CINECA
- [MEDIUM SEVERITY] The JSPUI "Edit News" feature (accessible to Administrators) can be used to view/edit ANY files which are readable to the Tomcat user account (DS-3063 - requires a JIRA account to access.)
- REST fixes
- OAI fixes
- Configuration Fixes
- Other minor fixes
In addition, this release fixes minor bugs in the 5.x releases. For more information, see the Changes in 5.x page.
5.5 Acknowledgments
The 5.5 release was led by Tim Donohue (DuraSpace) and the Committers.
The following individuals provided code or bug fixes to the 5.5 release: Pascal-Nicolas Becker (pnbecker), Andrea Bollini (abollini), Tim Donohue (tdonohue), Claudia Juergen (cjuergen), Bram Luyten (bram-atmire), Ivan Masar (helix84), Dylan Meeus (DylanMeeus), AmberPoo1, Christian Scheible (christian-scheible), Tim Van de Langenbergh (tim-atmire), Mark Wood (mwoodiupui)
5.4 Release Notes
Note | ||
---|---|---|
| ||
DSpace 5.4 contains security fixes for the JSPUI only. To ensure your 5.x site is secure, we highly recommend JSPUI DSpace 5.x users upgrade to DSpace 5.4. |
DSpace 5.4 is a bug fix release to resolve several issues found in DSpace 5.x. As it only provides bug fixes, DSpace 5.4 should constitute an easy upgrade from any other DSpace 5.x version for most users. Beginning with DSpace 5.x, we also provide an easier upgrade process from any prior version of DSpace (1.x.x, 3.x or 4.x).
Major bug fixes include:
- JSPUI security fixes:
- [MEDIUM SEVERITY] Cross-site scripting (XSS injection) is possible in JSPUI search interface (in Firefox web browser). (DS-2736 - requires a JIRA account to access for two weeks, and then will be public): This vulnerability could allow someone to embed dangerous Javascript code into links to search results. If a user was emailed such a link and clicked it, the javascript would be run in their local browser. This vulnerability has existed since DSpace 3.x
- Discovered by Genaro Contreras
- Discovered by Genaro Contreras
- [LOW SEVERITY] Expression language injection (EL Injection) is possible in JSPUI search interface. (DS-2737 - requires a JIRA account to access for two weeks, and then will be public): This vulnerability could allow someone to obtain information from the site/server using JSP syntax. This vulnerability has existed since DSpace 3.x
- Discovered by Genaro Contreras
- Discovered by Genaro Contreras
- [MEDIUM SEVERITY] Cross-site scripting (XSS injection) is possible in JSPUI search interface (in Firefox web browser). (DS-2736 - requires a JIRA account to access for two weeks, and then will be public): This vulnerability could allow someone to embed dangerous Javascript code into links to search results. If a user was emailed such a link and clicked it, the javascript would be run in their local browser. This vulnerability has existed since DSpace 3.x
- Google Scholar fix:
- Google Scholar metadata did not guarantee proper ordering of authors (DS-2679)
- Search / Browse fixes (for Discovery/Solr):
- Resolved a significant memory leak when searching/browsing (gradual leak) (DS-2869)
- Resolved a significant memory spike when reindexing (only triggered when running "index-discovery" with no arguments) (DS-2832)
- Fixes to allow fielded or boolean searches to work once again (DS-2699, DS-2803)
- Solr logging was broken. It did not properly log to the "
[dspace]/log/solr.log
" files (DS-2790)
- OAI-PMH fixes:
- REST API fixes:
Deposit/Submission fixes:
Minor fixes to XMLUI Mirage2 theme
In addition, this release fixes a variety of minor bugs in the 5.x releases. For more information, see the Changes in 5.x page.
5.4 Acknowledgments
The 5.4 release was led by Andrea Schweer (University of Waikato ITS), Tim Donohue and the Committers.
The following individuals provided code or bug fixes to the 5.4 release: Pascal-Nicolas Becker (pnbecker), Arnaud de Bossoreille (arnodb), Brad Dewar (bdewar), Peter Dietz (peterdietz), Tim Donohue (tdonohue), Ondrej Košarko (kosarko), Aleksander Kotynski-Buryla (akotynski), Ivan Masar (helix84), Hardy Pottinger (hardyoyo), Christian Scheible (christian-scheible), Andrea Schweer (aschweer), Bill Tantzen (wilee53), Jonas Van Goolen, Chris Wilper (cwilper), Mark H Wood (mwoodiupui), Jun Won Jung (RomanticCat)
5.3 Release Notes
DSpace 5.3 is a bug fix release to resolve several issues found in DSpace 5.2. As it only provides bug fixes, DSpace 5.3 should constitute an easy upgrade from DSpace 5.0, 5.1 or 5.2 for most users. Beginning with DSpace 5.x, we also provide an easier upgrade process from any prior version of DSpace (1.x.x, 3.x or 4.x).
Major bug fixes include:
- Security fixes:
- [LOW SEVERITY] Possible to access files attached to "in-progress" submissions via a direct link (DS-2614 - requires a JIRA account to access for two weeks, and then will be public). This vulnerability could allow anyone in the world to download a file attached to an "in-progress" submission if they are provided with a direct link to that file (from either UI). While a direct file link would be very hard to "guess" or stumble upon, this could allow an individual with deposit rights to make available content which has not been approved by local DSpace administrators. This vulnerability has at least existed since 5.0, but may effect versions as old as 3.0.
- Discovered by Pascal-Nicolas Becker of Technische Universität Berlin
- [LOW SEVERITY] Possible to access files attached to "in-progress" submissions via a direct link (DS-2614 - requires a JIRA account to access for two weeks, and then will be public). This vulnerability could allow anyone in the world to download a file attached to an "in-progress" submission if they are provided with a direct link to that file (from either UI). While a direct file link would be very hard to "guess" or stumble upon, this could allow an individual with deposit rights to make available content which has not been approved by local DSpace administrators. This vulnerability has at least existed since 5.0, but may effect versions as old as 3.0.
- Search and browse fixes:
- OAI fixes:
- Performing a full OAI import now also cleans the OAI cache (DS-2543)
- Harvested items are now properly imported in OAI (DS-2554)
- Tombstones (deleted item status) are now properly applied for withdrawn items (DS-2593)
(note: this requires 'import' to be run, the OAI event consumer will not create tombstones automatically) dc.date.available
is now properly exposed when using the mets metadata format (DS-2598)
- Authorization policy fixes:
- Custom policies for items in workspace or workflow (eg. embargo lifts) are now ignored by AuthorizeManager (DS-2614)
NULL
Resource Policy types (commonly found when upgrading from DSpace < 3.0) are now handled correctly by AuthorizeManager (DS-2587)- Item-level versioning now carries across all custom policies in new item versions (eg. embargos) (DS-2358)
- Other notable fixes:
- Optimized "Select Collection" query is now disabled by default as a workaround to ensure special group lookups (LDAP, Shibboleth, IP-based) work out-of-the-box (DS-2673)
- Resolved issue where citation_pdf_url metadata was NULL for items with multiple bitstreams but no primary bitstream (DS-2603)
dc.rights
metadata is now properly exposed in embedded XHTML head DC (DS-2568)
In addition, this release fixes a variety of minor bugs in the 5.x releases. For more information, see the Changes in 5.x page.
5.3 Acknowledgments
The 5.3 release was led by Kim Shepherd (University of Auckland Library) and the Committers.
The following individuals provided code or bug fixes to the 5.3 release: Roeland Dillen (rradillen), Tim Donohue (tdonohue), Ondřej Košarko (kosarko), Bram Luyten (bram-atmire), Pascal-Nicolas Becker (pnbecker), Pablo Buenaposada (pablobuenaposada), Nicolas Schwab (nicolasschwab), Andrea Schweer (aschweer), Àlex Magaz Graça (rivaldi8), junwei1229, and Claudia Juergen (cjuergen).
5.2 Release Notes
DSpace 5.2 is a bug fix release to resolve several issues found in DSpace 5.1. As it only provides bug fixes, DSpace 5.2 should constitute an easy upgrade from DSpace 5.0 or 5.1 for most users. Beginning with DSpace 5.x, we also provide an easier upgrade process from any prior version of DSpace (1.x.x, 3.x or 4.x).
Major bug fixes include:
- Solr statistics upgrade fixes:
- OAI fixes:
- Handle dates correctly in resumption tokens, so that harvesting captures the full specified range. (DS-2546, DS-2582)
- List all authors in METS formatted metadata. (DS-2474)
- Change the declared OAI deletion mode to "transient", which corresponds to what DSpace actually does. (DS-2491)
- Restore the ability to create additional Filters for OAI-PMH interface. (DS-2423)
- REST API fixes:
- Other notable fixes:
- "
dspace update-handle-prefix
" failed when using Oracle DB. (DS-2218) - Do not index items that are still in a submitter's workspace. (DS-2403)
- Remember the context (community, collection) during browsing. (DS-2482)
- Better handle upload of file with a semicolon in its name. (DS-2513)
- EZID DOI minting properly sets the URI of the identified item. (DS-2518)
- Update of the list of robots recognized by DSpace. (DS-2531)
- "
In addition, this release fixes a variety of minor bugs in the 5.x releases. For more information, see the Changes in 5.x page.
5.2 Acknowledgments
The 5.2 release was led by Hardy Pottinger (University of Missouri Library Systems) and the Committers.
The following individuals provided code or bug fixes to the 5.2 release: Pascal-Nicolas Becker (pnbecker), CTU Developers (ctu-developers), Roeland Dillen (rradillen), Tim Donohue (tdonohue), Àlex Magaz Graça (rivaldi8), Claudia Juergen (cjuergen), Ondřej Košarko (kosarko), Panagiotis Koutsourakis (kutsurak), Bram Luyten (bram-atmire), Ivan Masar (helix84), minusdavid, Hardy Pottinger (hardyoyo), Christian Scheible (christian-scheible), Andrea Schweer (aschweer), Antoine Snyers (antoine-atmire), Kevin Van de Velde (KevinVdV), Tim Van den Langenbergh (TimothyXL), Chris Wilper (cwilper), Mark Wood (mwoodiupui)
5.1 Release Notes
Note | ||
---|---|---|
| ||
DSpace 5.1 contains security fixes for both the XMLUI and JSPUI. To ensure your 5.x site is secure, we highly recommend all DSpace 5.x users upgrade to DSpace 5.1. We also highly recommend removing any "allowLinking=true" settings from your Tomcat's <Context> configuration. Previously our installation documentation erroneously listed examples which included "allowLinking=true", while the Tomcat documentation lists it as a possible security concern. The XMLUI Directory Traversal Vulnerability (see below) is also exacerbated by this setting. |
Info | ||
---|---|---|
| ||
Several of the security vulnerabilities patched in DSpace 5.1 (and backported to 4.3 and 3.4) also affect sites running unsupported DSpace 1.x.x releases. In order to ensure your site is patched, we highly recommend upgrading to DSpace 3.4, DSpace 4.3 or DSpace 5.1. If you are considering an upgrade from DSpace 1.x.x, note that, as of DSpace 5, your existing data (i.e. database contents, search/browse indexes) will now be automatically upgraded from ANY prior version of DSpace. Therefore, you may wish to consider upgrading directly to DSpace 5.1, as the 5.x upgrade process is simplified. |
DSpace 5.1 is a security and bug fix release to resolve several issues located in DSpace 5.0. As it only provides bug fixes, DSpace 5.1 should constitute an easy upgrade from DSpace 5.0 for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 5.0 to 5.1.
This release addresses the following security issues discovered in DSpace 5.x and below:
- XMLUI Security Fixes
[HIGH SEVERITY] XMLUI Directory Traversal Vulnerabilities (DS-2445 - requires a JIRA account to access for two weeks, and then will be public): These vulnerabilities allow someone to potentially access any file on your local filesystem which is readable to the Tomcat user account. This includes files which are unrelated to DSpace or Tomcat, but are readable to all users on the filesystem (e.g. /etc/passwd, /etc/hosts, etc.). This also includes Tomcat configuration files (which may or may not contain passwords). These vulnerabilities have existed since DSpace 1.5.2.
Discovered by: Khalil Shreateh, with additional (related) vulnerabilities discovered by the DSpace Committer Team
- In some configurations of Tomcat, simply removing any "allowLinking=true" settings from your Tomcat's <Context> configuration will limit the directory traversal vulnerability's severity to only allow access to files within the XMLUI web application directory. In addition, the Tomcat documentation details "allowLinking=true" as a possible security concern. However, you still must upgrade or patch your DSpace in order to completely resolve this vulnerability.
- JSPUI Security Fixes
- [MEDIUM SEVERITY] JSPUI Directory Traversal Vulnerability (DS-2448 - requires a JIRA account to access for two weeks, and then will be public): This vulnerability allows someone to potentially access any file within the JSPUI web application directory (e.g. WEB-INF/web.xml). This vulnerability is believed to have existed in all prior versions of DSpace.
- Discovered by Khalil Shreateh
- Discovered by Khalil Shreateh
- [LOW SEVERITY] Cross-site scripting (XSS injection) is possible in JSPUI Recent Submissions listings (DS-1702 - requires a JIRA account to access for two weeks, and then will be public): This vulnerability could allow a depositor/submitter to embed dangerous Javascript code into the metadata of a new submission, thus causing that code to be run across other user accounts. However, this vulnerability is only possible by someone with privileges to add content to your DSpace site. This vulnerability has existed since DSpace 1.5.x.
- Discovered by: Jean-Paul Zhao of University of Toronto
- Discovered by: Jean-Paul Zhao of University of Toronto
- [LOW SEVERITY] Cross-site scripting (XSS injection) is possible in JSPUI Discovery search form (DS-2044 - requires a JIRA account to access for two weeks, and then will be public): This vulnerability could allow someone to embed dangerous Javascript code into links to search results. If a user was emailed such a link and clicked it, the javascript would be run in their local browser. This vulnerability has existed since DSpace 3.x
- 4.x / 5.x vulnerability discovered by Gabriela Mircea of McMaster University and Khalil Shreateh
- 3.x vulnerability discovered by İlyas Orak of Biznet Bilisim A.S.
- [MEDIUM SEVERITY] JSPUI Directory Traversal Vulnerability (DS-2448 - requires a JIRA account to access for two weeks, and then will be public): This vulnerability allows someone to potentially access any file within the JSPUI web application directory (e.g. WEB-INF/web.xml). This vulnerability is believed to have existed in all prior versions of DSpace.
In addition, this release fixes a variety of minor bugs in the 5.0 release. For more information, see the Changes in 5.x page.
5.1 Acknowledgments
The 5.1 release was led by Tim Donohue (DuraSpace) and the Committers.
The following individuals provided code or bug fixes to the 5.1 release: CTU Developers (ctu-developers), Tim Donohue (tdonohue), Ondřej Košarko (kosarko), Pascal-Nicolas Becker (pnbecker), Claudia Juergen (cjuergen), Ivan Masar (helix84), Andrea Pascarelli (lap82), Hardy Pottinger (hardyoyo), Christian Scheible (christian-scheible), William Tantzen (wilee53), Mark Wood (mwoodiupui),
Major bug fixes include:
- Security fixes:
- [LOW SEVERITY] Possible to access files attached to "in-progress" submissions (DS-2614 - requires a JIRA account to access for two weeks, and then will be public). This vulnerability could allow anyone in the world to download a file attached to an "in-progress" submission if they are provided with a direct link to that file (from either UI). While a direct file link would be very hard to "guess" or stumble upon, this could allow an individual with deposit rights to make available content which has not been approved by local DSpace administrators. This vulnerability has at least existed since 5.0, but may effect versions as old as 3.0.
- Discovered by Pascal-Nicolas Becker of Technische Universität Berlin
- [LOW SEVERITY] Possible to access files attached to "in-progress" submissions (DS-2614 - requires a JIRA account to access for two weeks, and then will be public). This vulnerability could allow anyone in the world to download a file attached to an "in-progress" submission if they are provided with a direct link to that file (from either UI). While a direct file link would be very hard to "guess" or stumble upon, this could allow an individual with deposit rights to make available content which has not been approved by local DSpace administrators. This vulnerability has at least existed since 5.0, but may effect versions as old as 3.0.
- Search and browse fixes:
- OAI fixes:
- Performing a full OAI import now also cleans the OAI cache (DS-2543)
- Harvested items are now properly imported in OAI (DS-2554)
- Tombstones (deleted item status) are now properly applied for withdrawn items (DS-2593)
(note: this requires 'import' to be run, the OAI event consumer will not create tombstones automatically) dc.date.available
is now properly exposed when using the mets metadata format (DS-2598)
- Authorization policy fixes:
- Custom policies for items in workspace or workflow (eg. embargo lifts) are now ignored by AuthorizeManager (DS-2614)
NULL
Resource Policy types (commonly found when upgrading from DSpace < 3.0) are now handled correctly by AuthorizeManager (DS-2587)- Item-level versioning now carries across all custom policies in new item versions (eg. embargos) (DS-2358)
- Other notable fixes:
- Optimized "Select Collection" query is now disabled by default as a workaround to ensure special group lookups (LDAP, Shibboleth, IP-based) work out-of-the-box (DS-2673)
- Resolved issue where citation_pdf_url metadata was NULL for items with multiple bitstreams but no primary bitstream (DS-2603)
dc.rights metadata
is now properly exposed in embedded XHTML head DC (DS-2568)
In addition, this release fixes a variety of minor bugs in the 5.x releases. For more information, see the Changes in 5.x page.
5.2 Release Notes
DSpace 5.2 is a bug fix release to resolve several issues found in DSpace 5.1. As it only provides only bug fixes, DSpace 5.2 should constitute an easy upgrade from DSpace 5.0 or 5.1 for most users. Beginning with DSpace 5.x, we also provide an easier upgrade process from any prior version of DSpace (1.x.x, 3.x or 4.x).
Major bug fixes include:
- Solr statistics upgrade fixes:
- OAI fixes:
- Handle dates correctly in resumption tokens, so that harvesting captures the full specified range. (DS-2546, DS-2582)
- List all authors in METS formatted metadata. (DS-2474)
- Change the declared OAI deletion mode to "transient", which corresponds to what DSpace actually does. (DS-2491)
- Restore the ability to create additional Filters for OAI-PMH interface. (DS-2423)
- REST API fixes:
- Other notable fixes:
- "
dspace update-handle-prefix
" failed when using Oracle DB. (DS-2218) - Do not index items that are still in a submitter's workspace. (DS-2403)
- Remember the context (community, collection) during browsing. (DS-2482)
- Better handle upload of file with a semicolon in its name. (DS-2513)
- EZID DOI minting properly sets the URI of the identified item. (DS-2518)
- "
- Update of the list of robots recognized by DSpace. (DS-2531)
- Update of the list of robots recognized by DSpace. (DS-2531)
In addition, this release fixes a variety of minor bugs in the 5.x releases. For more information, see the Changes in 5.x page.
5.1 Release Notes
Note | ||
---|---|---|
| ||
DSpace 5.1 contains security fixes for both the XMLUI and JSPUI. To ensure your 5.x site is secure, we highly recommend all DSpace 5.x users upgrade to DSpace 5.1. We also highly recommend removing any "allowLinking=true" settings from your Tomcat's <Context> configuration. Previously our installation documentation erroneously listed examples which included "allowLinking=true", while the Tomcat documentation lists it as a possible security concern. The XMLUI Directory Traversal Vulnerability (see below) is also exacerbated by this setting. |
Info | ||
---|---|---|
| ||
Several of the security vulnerabilities patched in DSpace 5.1 (and backported to 4.3 and 3.4) also affect sites running unsupported DSpace 1.x.x releases. In order to ensure your site is patched, we highly recommend upgrading to DSpace 3.4, DSpace 4.3 or DSpace 5.1. If you are considering an upgrade from DSpace 1.x.x, note that, as of DSpace 5, your existing data (i.e. database contents, search/browse indexes) will now be automatically upgraded from ANY prior version of DSpace. Therefore, you may wish to consider upgrading directly to DSpace 5.1, as the 5.x upgrade process is simplified. |
DSpace 5.1 is a security and bug fix release to resolve several issues located in DSpace 5.0. As it only provides only bug fixes, DSpace 5.1 should constitute an easy upgrade from DSpace 5.0 for most users. No database changes or additional configuration changes should be necessary when upgrading from DSpace 5.0 to 5.1.
This release addresses the following security issues discovered in DSpace 5.x and below:
- XMLUI Security Fixes
[HIGH SEVERITY] XMLUI Directory Traversal Vulnerabilities (DS-2445 - requires a JIRA account to access for two weeks, and then will be public): These vulnerabilities allow someone to potentially access any file on your local filesystem which is readable to the Tomcat user account. This includes files which are unrelated to DSpace or Tomcat, but are readable to all users on the filesystem (e.g. /etc/passwd, /etc/hosts, etc.). This also includes Tomcat configuration files (which may or may not contain passwords). These vulnerabilities have existed since DSpace 1.5.2.
Discovered by: Khalil Shreateh, with additional (related) vulnerabilities discovered by the DSpace Committer Team
- In some configurations of Tomcat, simply removing any "allowLinking=true" settings from your Tomcat's <Context> configuration will limit the directory traversal vulnerability's severity to only allow access to files within the XMLUI web application directory. In addition, the Tomcat documentation details "allowLinking=true" as a possible security concern. However, you still must upgrade or patch your DSpace in order to completely resolve this vulnerability.
- JSPUI Security Fixes
- [MEDIUM SEVERITY] JSPUI Directory Traversal Vulnerability (DS-2448 - requires a JIRA account to access for two weeks, and then will be public): This vulnerability allows someone to potentially access any file within the JSPUI web application directory (e.g. WEB-INF/web.xml). This vulnerability is believed to have existed in all prior versions of DSpace.
- Discovered by Khalil Shreateh
- Discovered by Khalil Shreateh
- [LOW SEVERITY] Cross-site scripting (XSS injection) is possible in JSPUI Recent Submissions listings (DS-1702 - requires a JIRA account to access for two weeks, and then will be public): This vulnerability could allow a depositor/submitter to embed dangerous Javascript code into the metadata of a new submission, thus causing that code to be run across other user accounts. However, this vulnerability is only possible by someone with privileges to add content to your DSpace site. This vulnerability has existed since DSpace 1.5.x.
- Discovered by: Jean-Paul Zhao of University of Toronto
- Discovered by: Jean-Paul Zhao of University of Toronto
- [LOW SEVERITY] Cross-site scripting (XSS injection) is possible in JSPUI Discovery search form (DS-2044 - requires a JIRA account to access for two weeks, and then will be public): This vulnerability could allow someone to embed dangerous Javascript code into links to search results. If a user was emailed such a link and clicked it, the javascript would be run in their local browser. This vulnerability has existed since DSpace 3.x
- 4.x / 5.x vulnerability discovered by Gabriela Mircea of McMaster University and Khalil Shreateh
- 3.x vulnerability discovered by İlyas Orak of Biznet Bilisim A.S.
- [MEDIUM SEVERITY] JSPUI Directory Traversal Vulnerability (DS-2448 - requires a JIRA account to access for two weeks, and then will be public): This vulnerability allows someone to potentially access any file within the JSPUI web application directory (e.g. WEB-INF/web.xml). This vulnerability is believed to have existed in all prior versions of DSpace.
In addition, this release fixes a variety of minor bugs in the 5.0 release. For more information, see the Changes in 5.x page.
5.0 Release Notes
The following is a list of the new features included for the 5.x platform (not an exhaustive list):
...
A full list of all changes / bug fixes in 5.x is available in the Changes in 5.x section.
Acknowledgments
The following individuals have contributed directly to this release of DSpace:
DSpace 5.0, 5.1 and 5.2 Acknowledgments
The following individuals provided code or bug fixes to the 5.0 release: contributed directly to this release of DSpace: Adan Roman, Àlex Magaz Graça , Andrea Bollini, Andrea Schweer, Antoine Snyers, Art Lowel, Artur Konczak, Bavo Van Geit, Bram Luyten, Christian Scheible, Christian Völker, Christos Rhodosthenous, Claudia Jürgen , CTU Developers, Denis Fdz, Ed Goulet, Eliana de Mattos Pinto Coelho, Elvi S. Nemiz, Emilio Lorenzo, George Simeonov, Graham Triggs , Hardy Pottinger, Ivan Masár, James Halliday, João Melo, Jon Gibson , Jordan Piščanc, Jozef M. , Keiji Suzuki, Kevin Van de Velde, Kostas Stamatis, Luigi Andrea Pascarelli, Marina Muilwijk, Mark Diggory, Mark H. Wood, Mohamed Mohideen Abdul Rasheed, Monika Mevenkamp, Ondřej Košarko, Panagiotis Koutsourakis, Pascal-Nicolas Becker, Pauline Ward, Paulo Graça , Peter Dietz, Petya Kohts, Philip Vissenaekens, Robert Faling, Robin Taylor, Roeland Dillen, Royopa, Sonmez CELIK, Terry Brady, Thanos Kyritsis, Thomas Misilo, Tiago Murakami, Tim Donohue, and others who reviewed and commented on their work. Many of these could not do this work without the support (release time and financial) of their associated institutions. We offer thanks to those institutions for supporting their staff to take time to contribute to the DSpace project.
Additional Thanks
A big thank you also goes out to the DSpace Community Advisory Team (DCAT), who helped the developers to prioritize and plan out several of the new features that made it into this release. The current DCAT members include: Augustine Gitonga, Bram Luyten, Bharat Chaudhari, Claire Bundy, Dibyendra Hyoju, Elin Stangeland, Felicity A Dykas, Iryna Kuchma, James Evans, Jim Ottaviani, Kate Dohe, Kathleen Schweitzberger, Leonie Hayes, Lilly Li, Maureen Walsh, Pauline Ward, Roger Weaver, Sarah Molloy, Sarah Potvin, Sarah Shreeves, Steve Van Tuyl, Terry Brady, Valorie Hollister and Yan Han.
...
Want to see your name appear in our list of contributors? All you have to do is report an issue, fix a bug, improve our documentation or help us determine the necessary requirements for a new feature! Visit our Issue Tracker to report a bug, or join dspace-devel mailing list to take part in development work. If you'd like to help improve our current documentation, please get in touch with one of our Committers with your ideas. You don't even need to be a developer! Repository managers can also get involved by volunteering to join the DSpace Community Advisory Team and helping our developers to plan new features.
...
- Peter Dietz (Longsight)
- Hardy Pottinger (University of Missouri Library Systems)
- Ivan Masár
- Mark H. Wood (Indiana University-Purdue University Indianapolis)
- Robin Taylor (University of Edinburgh)
- Pascal-Nicolas Becker (Technische Universität Berlin)
- Andrea Schweer (Library Consortium of New Zealand)
...
- )
...
The 5.2 release was led by Hardy Pottinger (University of Missouri Library Systems) and the Committers.
...
Additional thanks to Tim Donohue from DuraSpace for keeping all of us focused on the work at hand, for calming us when we got excited, and for the general support for the DSpace project.
...