Race Condition leading to logging errors
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
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-22047US | low3.1 | — | ||
A race condition exists in Audited 4.0.0 to 5.3.3 that can result in an authenticated user to cause audit log entries to be attributed to another user. | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/collectiveidea/auditedPACKAGE
- https://github.com/collectiveidea/audited/commit/342734c9396d8f96d3165f1d8531c626139fa4c6WEB
- https://github.com/collectiveidea/audited/issues/601WEB
- https://github.com/collectiveidea/audited/pull/669WEB
- https://github.com/collectiveidea/audited/pull/671WEB
- https://github.com/collectiveidea/audited/security/advisories/GHSA-hjp3-5g2q-7jwwWEB
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/audited/CVE-2024-22047.ymlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2024-22047ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan