vitess.io/vitess vulnerabilities
- Registry
- Go
- Latest
- 0.24.5
15 known advisories
The latest version, 0.24.5, is not affected by any of them. Projects on older versions may be.
go get vitess.io/vitess@v0.24.5Is your project on an affected vitess.io/vitess?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for vitess.io/vitess
Vitess vttablet /twopcz reflected XSS in vitess.io/vitess
- Affected
- <0.23.5 · >=0.24.0 <0.24.2
- Fixed in
- 0.23.5, 0.24.2
Vitess vttablet /twopcz reflected XSS
- Affected
- <0.23.5 · >=0.24.0 <0.24.2
- Fixed in
- 0.23.5, 0.24.2
Missing authorization on vttablet /debug/vrlog in vitess.io/vitess
- Affected
- <0.23.6 · >=0.24.0-rc1 <0.24.3
- Fixed in
- 0.23.6, 0.24.3
Vitess: Missing authorization on vttablet /debug/vrlog exposes live VReplication SQL data
- Affected
- >=0.24.0-rc1 <=0.24.2 · <=0.23.6
- Fixed in
- No fix released
Vitess users can gain unauthorized access to production deployment environments in vitess.io/vitess
- Affected
- <0.22.4 · >=0.23.0 <0.23.3
- Fixed in
- 0.22.4, 0.23.3
Vitess users with backup storage access can write to arbitrary file paths in vitess.io/vitess
- Affected
- <0.22.4 · >=0.23.0-rc1 <0.23.3
- Fixed in
- 0.22.4, 0.23.3
Vitess users with backup storage access can write to arbitrary file paths on restore
- Affected
- >=0.23.0-rc1 <0.23.3 · <0.22.4
- Fixed in
- 0.22.4, 0.23.3
Vitess users with backup storage access can gain unauthorized access to production deployment environments
- Affected
- <=0.23.2
- Fixed in
- No fix released
Vitess allows HTML injection in /debug/querylogz and /debug/env in vitess.io/vitess
- Affected
- <0.19.8 · >=0.20.0 <0.20.4 · >=0.21.0 <0.21.1
- Fixed in
- 0.19.8, 0.20.4, 0.21.1
Vitess allows HTML injection in /debug/querylogz & /debug/env
- Affected
- >=0.21.0-rc1 <0.21.1 · >=0.20.0-rc1 <0.20.4 · <0.19.8
- Fixed in
- 0.19.8, 0.20.4, 0.21.1
Denial of service attack by triggering unbounded memory usage in vitess.io/vitess
- Affected
- <0.17.7 · >=0.18.0 <0.18.5 · >=0.19.0 <0.19.4
- Fixed in
- 0.17.7, 0.18.5, 0.19.4
Vitess vulnerable to infinite memory consumption and vtgate crash
- Affected
- <0.17.7 · >=0.18.0 <0.18.5 · >=0.19.0 <0.19.4
- Fixed in
- 0.17.7, 0.18.5, 0.19.4
VTAdmin users that can create shards can deny access to other functions
- Affected
- <0.16.2
- Fixed in
- 0.16.2
Improper handling of keyspaces in vitess.io/vitess
- Affected
- <0.16.1
- Fixed in
- 0.16.1
vitess allows users to create keyspaces that can deny access to already existing keyspaces
- Affected
- <0.16.1
- Fixed in
- 0.16.1
Is your vitess.io/vitess version vulnerable?
- vitess.io/vitess 2.1No known advisories in 2.1.1
- vitess.io/vitess 2.0No known advisories in 2.0.0
- vitess.io/vitess 0.24No known advisories in 0.24.5
- vitess.io/vitess 0.23No known advisories in 0.23.8
- vitess.io/vitess 0.225 advisories in 0.22.4
- vitess.io/vitess 0.218 advisories in 0.21.6
- vitess.io/vitess 0.208 advisories in 0.20.8
- vitess.io/vitess 0.198 advisories in 0.19.10
Which of your client projects still run an old vitess.io/vitess?
NPMscan reads the go.mod 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 Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.