concurrent-ruby vulnerabilities
Modern concurrency tools including agents, futures, promises, thread pools, actors, supervisors, and more. Inspired by Erlang, Clojure, Go, JavaScript, actors, and classic concurrency patterns.
- Registry
- RubyGems
- Latest
- 1.3.8
- License
- MIT
3 known advisories
The latest version, 1.3.8, is not affected by any of them. Projects on older versions may be.
bundle update --conservative concurrent-ruby # Gemfile: '>= 1.3.8'Is your project on an affected concurrent-ruby?
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 concurrent-ruby
Concurrent Ruby: ReadWriteLock allows wrong-thread write release and stray read-release counter corruption
- Affected
- <1.3.7
- Fixed in
- 1.3.7
Concurrent Ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity
- Affected
- <1.3.7
- Fixed in
- 1.3.7
Concurrent Ruby : `AtomicReference#update` livelocks when the stored value is `Float::NAN`
- Affected
- <1.3.7
- Fixed in
- 1.3.7
Is your concurrent-ruby version vulnerable?
- concurrent-ruby 1.3No known advisories in 1.3.8
- concurrent-ruby 1.23 advisories in 1.2.3
- concurrent-ruby 1.13 advisories in 1.1.10
- concurrent-ruby 1.03 advisories in 1.0.5
- concurrent-ruby 0.93 advisories in 0.9.2
- concurrent-ruby 0.83 advisories in 0.8.0
- concurrent-ruby 0.73 advisories in 0.7.2
- concurrent-ruby 0.63 advisories in 0.6.1
- concurrent-ruby 0.53 advisories in 0.5.0
- concurrent-ruby 0.43 advisories in 0.4.1
Which of your client projects still run an old concurrent-ruby?
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.