globalid vulnerabilities
URIs for your models makes it easy to pass references around.
- Registry
- RubyGems
- Latest
- 1.4.0
- License
- MIT
1 known advisory
The latest version, 1.4.0, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
bundle update --conservative globalid # Gemfile: '>= 1.4.0'Is your project on an affected globalid?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for globalid
ReDoS based DoS vulnerability in GlobalID
- Affected
- >=0.2.1 <1.0.1
- Fixed in
- 1.0.1
Is your globalid version vulnerable?
- globalid 1.4No known advisories in 1.4.0
- globalid 1.3No known advisories in 1.3.0
- globalid 1.2No known advisories in 1.2.1
- globalid 1.1No known advisories in 1.1.0
- globalid 1.0No known advisories in 1.0.1
- globalid 0.61 advisory in 0.6.0
- globalid 0.51 advisory in 0.5.2
- globalid 0.41 advisory in 0.4.2
- globalid 0.31 advisory in 0.3.7
- globalid 0.21 advisory in 0.2.3
Which of your client projects still run an old globalid?
NPMscan reads the Gemfile.lock 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 RubyGems packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the RubyGems registry.