Sensitive fields nested in embedded values are not redacted in AshPaperTrail versions
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 0.7.0 and 0cd4acfe7f48397673d8594fb5e2cd0f1bda6e40.
Cleartext Storage of Sensitive Information vulnerability in ash-project ash_paper_trail allows an attacker with read access to the generated version resource to recover sensitive values nested inside embedded resources, unions, or lists. sensitive_attributes :redact and :ignore only act on the tracked resource's top-level attributes. maybe_redact_changes/3 and the stored-action-input path in AshPaperTrail.Resource.Changes.CreateNewVersion derive the sensitive set from the resource's own attributes and never descend into embedded, union, or list values, so a non-sensitive attribute or action argument that holds an embed with a sensitive? field (for example an accepted credentials embed carrying a token) is written to the version table in cleartext. This issue affects ash_paper_trail: from 0.3.0 before 0.7.0.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ash-project | >=0.3.0 <0.7.0, >=ffe5e03b14d26b73bff17f3eca811591788aba9c <0cd4acfe7f48397673d8594fb5e2cd0f1bda6e40 | 0.7.0, 0cd4acfe7f48397673d8594fb5e2cd0f1bda6e40 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket