DSpace: Curation Task Reporter output path is not restricted to trusted directories (Path Traversal Vulnerability)
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.6.7, 8.4, 9.3, 10.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
DSpace open source software is a repository application which provides durable access to digital resources. Prior to versions 7.6.7, 8.4, 9.3, and 10.0, the Curation Task feature allows an output path to be used by the reporter (-r parameter), typically used to stream results and status of curation task operations. It is not restricted to any particular base path, meaning that any path writable by the DSpace (often 'tomcat') user is allowed. This constitutes a Path Traversal Vulnerability in the curate script. This issue has been patched in versions 7.6.7, 8.4, 9.3, and 10.0.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- DSpace DSpace
fixed in 7.6.7; From 8.0-rc1 · fixed in 8.4; From 9.0-rc1 · fixed in 9.3
- org.dspace:dspace-apiMaven
fixed in 7.6.7
- org.dspace:dspace-apiMaven
From 8.0-rc1 · fixed in 8.4
- org.dspace:dspace-apiMaven
From 9.0-rc1 · fixed in 9.3
- org.dspace:dspace-apiMaven
From 10-rc1 · fixed in 10.0