io.vertx:vertx-core vulnerabilities
- Registry
- Maven
- Latest
- 5.2.3
7 known advisories
The latest version, 5.2.3, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=io.vertx:vertx-core -DdepVersion=5.2.3 -DforceVersion=trueIs your project on an affected io.vertx:vertx-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for io.vertx:vertx-core
Vert.x has a DoS via unbounded server-side SNI SslContext cache growth
- Affected
- >=4.3.4 <=4.3.8 · >=4.4.0 <=4.4.9 · >=4.5.0 <4.5.27 · >=5.0.0 <5.0.12
- Fixed in
- 4.5.27, 5.0.12
Vert.x Web static handler component cache can be manipulated to deny the access to static files
- Affected
- <4.5.24 · >=5.0.0.CR1 <5.0.7
- Fixed in
- 4.5.24, 5.0.7
Eclipse Vert.x vulnerable to a memory leak in TCP servers
- Affected
- >=4.3.4 <4.4.8 · >=4.5.0 <4.5.3
- Fixed in
- 4.4.8, 4.5.3
Eclipse Vert.x memory leak
- Affected
- >=4.5.0 <4.5.2 · >=4.4.5 <4.4.7
- Fixed in
- 4.4.7, 4.5.2
Moderate severity vulnerability that affects io.vertx:vertx-core
- Affected
- >=3.0.0 <3.5.2
- Fixed in
- 3.5.2
Moderate severity vulnerability that affects io.vertx:vertx-core
- Affected
- >=3.5.0 <3.5.4
- Fixed in
- 3.5.4
Excessive memory allocation
- Affected
- >=3.0.0 <3.5.4
- Fixed in
- 3.5.4
Is your io.vertx:vertx-core version vulnerable?
- io.vertx:vertx-core 5.2No known advisories in 5.2.3
- io.vertx:vertx-core 5.1No known advisories in 5.1.10
- io.vertx:vertx-core 5.0No known advisories in 5.0.12
- io.vertx:vertx-core 4.5No known advisories in 4.5.36
- io.vertx:vertx-core 4.42 advisories in 4.4.9
- io.vertx:vertx-core 4.33 advisories in 4.3.8
- io.vertx:vertx-core 4.21 advisory in 4.2.7
- io.vertx:vertx-core 4.11 advisory in 4.1.8
- io.vertx:vertx-core 4.01 advisory in 4.0.3
- io.vertx:vertx-core 3.91 advisory in 3.9.16
- io.vertx:vertx-core 3.81 advisory in 3.8.5
- io.vertx:vertx-core 3.71 advisory in 3.7.1
- io.vertx:vertx-core 3.61 advisory in 3.6.3
- io.vertx:vertx-core 3.51 advisory in 3.5.4
- io.vertx:vertx-core 3.43 advisories in 3.4.2
Which of your client projects still run an old io.vertx:vertx-core?
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.