org.dspace:dspace-api vulnerabilities
DSpace core data model and service APIs.
- Registry
- Maven
- Latest
- 10.1
8 known advisories
The latest version, 10.1, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.dspace:dspace-api -DdepVersion=10.1 -DforceVersion=trueIs your project on an affected org.dspace:dspace-api?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.dspace:dspace-api
DSpace: Path Traversal is possible through LDN message generation
- Affected
- >=8.0-rc1 <8.4 · >=9.0-rc1 <9.3 · >=10.0-rc1 <10.0
- Fixed in
- 8.4, 9.3, 10.0
DSpace: ORE resource URI does not validate scheme for non-web resources
- Affected
- <7.6.7 · >=8.0-rc1 <8.4 · >=9.0-rc1 <9.3 · >=10-rc1 <10.0
- Fixed in
- 7.6.7, 8.4, 9.3, 10.0
DSpace has a possible Path Traversal Vulnerability in its Curation Task Reporter output path
- Affected
- <7.6.7 · >=8.0-rc1 <8.4 · >=9.0-rc1 <9.3 · >=10-rc1 <10.0
- Fixed in
- 7.6.7, 8.4, 9.3, 10.0
DSpace has possible Remote Code Execution (RCE) through Velocity Templates used by LDN
- Affected
- >=8.0-rc1 <8.4 · >=9.0-rc1 <9.3 · >=10.0-rc1 <10.0
- Fixed in
- 8.4, 9.3, 10.0
DSpace is vulnerable to Path Traversal attacks when importing packages using Simple Archive Format
- Affected
- <7.6.4 · >=8.0 <8.2 · >=9.0 <9.1
- Fixed in
- 7.6.4, 8.2, 9.1
DSpace is vulnerable to XML External Entity injection during archive imports
- Affected
- <7.6.4 · >=8.0 <8.2 · >=9.0 <9.1
- Fixed in
- 7.6.4, 8.2, 9.1
DSpace ItemImportService API Vulnerable to Path Traversal in Simple Archive Format Package Import
- Affected
- >=4.0 <5.11 · >=6.0 <6.4
- Fixed in
- 5.11, 6.4
Communities and collections administrators can escalate their privilege up to system administrator
- Affected
- >=7.0 <7.1
- Fixed in
- 7.1
Is your org.dspace:dspace-api version vulnerable?
- org.dspace:dspace-api 10.1No known advisories in 10.1.0
- org.dspace:dspace-api 10.0No known advisories in 10.0.0
- org.dspace:dspace-api 9.4No known advisories in 9.4.0
- org.dspace:dspace-api 9.3No known advisories in 9.3.0
- org.dspace:dspace-api 9.24 advisories in 9.2.0
- org.dspace:dspace-api 9.14 advisories in 9.1.0
- org.dspace:dspace-api 9.06 advisories in 9.0.0
- org.dspace:dspace-api 8.5No known advisories in 8.5.0
- org.dspace:dspace-api 8.4No known advisories in 8.4.0
- org.dspace:dspace-api 8.34 advisories in 8.3.0
- org.dspace:dspace-api 8.24 advisories in 8.2.0
- org.dspace:dspace-api 8.16 advisories in 8.1.0
- org.dspace:dspace-api 8.06 advisories in 8.0.0
Which of your client projects still run an old org.dspace:dspace-api?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.