HighGHSA-q2qw-rmrh-vv42CVE-2018-16476

Improper Access Control in activejob

Published 5 Dec 2018 · Updated 17 Feb 2024

Is your project on an affected activejob?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

activejobRubyGems
Affected
>=4.2.0 <4.2.11
Fixed in
4.2.11
Update to the fixed version for your release line, for example:bundle update --conservative activejob # Gemfile: '>= 4.2.11'
activejobRubyGems
Affected
>=5.0.0 <5.0.7.1
Fixed in
5.0.7.1
Update to the fixed version for your release line, for example:bundle update --conservative activejob # Gemfile: '>= 5.0.7.1'
activejobRubyGems
Affected
>=5.1.0 <5.1.6.1
Fixed in
5.1.6.1
Update to the fixed version for your release line, for example:bundle update --conservative activejob # Gemfile: '>= 5.1.6.1'
activejobRubyGems
Affected
>=5.2.0 <5.2.1.1
Fixed in
5.2.1.1
Update to the fixed version for your release line, for example:bundle update --conservative activejob # Gemfile: '>= 5.2.1.1'

Details

A Broken Access Control vulnerability in Active Job versions >= 4.2.0 allows an attacker to craft user input which can cause Active Job to deserialize it using GlobalId and give them access to information that they should not have.

Is GHSA-q2qw-rmrh-vv42 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected activejob, and gives you the command that fixes it.

More advisories for activejob

activejob security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.