Impact
Metadata on a withdrawn Item is exposed via the XMLUI "mets.xml" object, as long as you know the handle/URL of the withdrawn Item. This vulnerability only impacts the XMLUI.
However, this vulnerability is very low severity as Item metadata does not tend to contain highly secure or sensitive information.
This vulnerability does NOT impact the JSPUI or 7.x.
Patches
Because of the low severity of this security issue, it requires updating to 6.4 to resolve. No patch is available for 5.x or below.
DSpace 6.x:
Apply the patch to your DSpace
If at all possible, we recommend upgrading your DSpace site based on the upgrade instructions. However, if you are unable to do so, you can manually apply the above patches as follows:
- Download the appropriate patch file to the machine where DSpace is running
- From the
[dspace-src] folder, apply the patch, e.g. git apply [name-of-file].patch
- Now, update your DSpace site (based loosely on the Upgrade instructions). This generally involves three steps:
- Rebuild DSpace, e.g.
mvn -U clean package (This will recompile all DSpace code)
- Redeploy DSpace, e.g.
ant update (This will copy all updated WARs / configs to your installation directory). Depending on your setup you also may need to copy the updated WARs over to your Tomcat webapps folder.
- Restart Tomcat
Workaround
If there are any withdrawn items which are known to have highly secure information in their metadata, they can be permanently deleted. This will ensure their secure metadata is inaccessible & removed from the system entirely.
References
Discovered & reported by David Cavrenne of Atmire
For more information
If you have any questions or comments about this advisory:
References
Impact
Metadata on a withdrawn Item is exposed via the XMLUI "mets.xml" object, as long as you know the handle/URL of the withdrawn Item. This vulnerability only impacts the XMLUI.
However, this vulnerability is very low severity as Item metadata does not tend to contain highly secure or sensitive information.
This vulnerability does NOT impact the JSPUI or 7.x.
Patches
Because of the low severity of this security issue, it requires updating to 6.4 to resolve. No patch is available for 5.x or below.
DSpace 6.x:
Apply the patch to your DSpace
If at all possible, we recommend upgrading your DSpace site based on the upgrade instructions. However, if you are unable to do so, you can manually apply the above patches as follows:
[dspace-src]folder, apply the patch, e.g.git apply [name-of-file].patchmvn -U clean package(This will recompile all DSpace code)ant update(This will copy all updated WARs / configs to your installation directory). Depending on your setup you also may need to copy the updated WARs over to your Tomcat webapps folder.Workaround
If there are any withdrawn items which are known to have highly secure information in their metadata, they can be permanently deleted. This will ensure their secure metadata is inaccessible & removed from the system entirely.
References
Discovered & reported by David Cavrenne of Atmire
For more information
If you have any questions or comments about this advisory:
References