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: collectiveidea/audited#601
• So the solution was implemented in the following Pull Request: collectiveidea/audited#669
• And the feature was published in version 5.3.3: RELEASE: collectiveidea/audited#671

References

• GHSA-hjp3-5g2q-7jww
• collectiveidea/audited#601
• collectiveidea/audited#669
• collectiveidea/audited#671
• https://nvd.nist.gov/vuln/detail/CVE-2024-22047
• collectiveidea/audited@342734c
• https://github.com/rubysec/ruby-advisory-db/blob/master/gems/audited/CVE-2024-22047.yml