LOW 3.1 RubyGems
Race Condition leading to logging errors
GHSA-hjp3-5g2q-7jww · CVE-2024-22047
Published · Modified
Description
In certain setups with threaded web servers, Audited's use of Thread.current can incorrectly attributed audits to the wrong user.
Fixed in 5.3.3.
In March, @convisoappsec noticed that the library in question had a Race Condition problem, which caused logs to be registered at times with different users than those who performed the genuine actions.
- The first issue we identified was from November 2021: https://github.com/collectiveidea/audited/issues/601
- So the solution was implemented in the following Pull Request: https://github.com/collectiveidea/audited/pull/669
- And the feature was published in version 5.3.3: RELEASE: https://github.com/collectiveidea/audited/pull/671
References
- WEB https://github.com/collectiveidea/audited/security/advisories/GHSA-hjp3-5g2q-7jww
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2024-22047
- WEB https://github.com/collectiveidea/audited/issues/601
- WEB https://github.com/collectiveidea/audited/pull/669
- WEB https://github.com/collectiveidea/audited/pull/671
- WEB https://github.com/collectiveidea/audited/commit/342734c9396d8f96d3165f1d8531c626139fa4c6
- PACKAGE https://github.com/collectiveidea/audited
- WEB https://github.com/rubysec/ruby-advisory-db/blob/master/gems/audited/CVE-2024-22047.yml
Ready to move
Start Securing
Free, no credit card | First findings in minutes