org.springframework.data:spring-data-commons vulnerabilities
Core Spring concepts underpinning every Spring Data module.
- Registry
- Maven
- Latest
- 4.1.2
7 known advisories
The latest version, 4.1.2, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.springframework.data:spring-data-commons -DdepVersion=4.1.2 -DforceVersion=trueIs your project on an affected org.springframework.data:spring-data-commons?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.springframework.data:spring-data-commons
Spring Data: Unbounded property-path cache keyed by externally-supplied path string
- Affected
- >=4.0.0 <4.0.6 · >=3.5.0 <3.5.12 · >=3.4.0 <=3.4.13
- Fixed in
- 3.5.12, 4.0.6
Spring Data Commons: Denial of Service via excessive memory allocation in projection binding
- Affected
- >=4.0.0 <4.0.6 · >=3.5.0 <3.5.12 · >=3.4.0 <=3.4.14 · >=3.0.0 <=3.3.16 · <=2.7.19
- Fixed in
- 3.5.12, 4.0.6
Spring Data Commons: Heap exhaustion from unbounded property-lookup cache retaining crafted string keys
- Affected
- >=4.0.0 <4.0.6 · >=3.5.0 <3.5.12 · >=3.4.0 <=3.4.14 · >=3.3.0 <=3.3.16 · <=2.7.19
- Fixed in
- 3.5.12, 4.0.6
Spring Data Commons: StackOverflowException when parsing Sort parameters (DoS)
- Affected
- >=4.0.0 <4.0.6 · >=3.5.0 <3.5.12 · >=3.4.0 <=3.4.14 · >=3.0.0 <=3.3.16 · <=2.7.19
- Fixed in
- 3.5.12, 4.0.6
Spring Data Commons contain a property path parser vulnerability caused by unlimited resource allocation
- Affected
- <1.13.11 · >=2.0.0 <2.0.6
- Fixed in
- 1.13.11, 2.0.6
Spring Data Commons, used in combination with XMLBeam, contains a property binder vulnerability caused by improper restriction of XML external entity references
- Affected
- >=1.13.0 <1.13.12 · >=2.0.0 <2.0.7
- Fixed in
- 1.13.12, 2.0.7
Spring Data Commons remote code injection vulnerability
- Affected
- >=1.13.0 <1.13.11 · >=2.0.0 <2.0.6
- Fixed in
- 1.13.11, 2.0.6
Is your org.springframework.data:spring-data-commons version vulnerable?
- org.springframework.data:spring-data-commons 4.1No known advisories in 4.1.2
- org.springframework.data:spring-data-commons 4.0No known advisories in 4.0.8
- org.springframework.data:spring-data-commons 3.5No known advisories in 3.5.13
- org.springframework.data:spring-data-commons 3.44 advisories in 3.4.13
- org.springframework.data:spring-data-commons 3.33 advisories in 3.3.13
- org.springframework.data:spring-data-commons 3.22 advisories in 3.2.12
- org.springframework.data:spring-data-commons 3.12 advisories in 3.1.12
- org.springframework.data:spring-data-commons 3.02 advisories in 3.0.12
- org.springframework.data:spring-data-commons 2.73 advisories in 2.7.18
- org.springframework.data:spring-data-commons 2.63 advisories in 2.6.10
- org.springframework.data:spring-data-commons 2.53 advisories in 2.5.12
- org.springframework.data:spring-data-commons 2.43 advisories in 2.4.15
- org.springframework.data:spring-data-commons 2.33 advisories in 2.3.9
- org.springframework.data:spring-data-commons 2.23 advisories in 2.2.13
Which of your client projects still run an old org.springframework.data:spring-data-commons?
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.