SQL string_trim removes only spaces, diverging from in-memory trimming in AshSql
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.1 and 1b11b5d8bc5321e2e6acac21594ef08f61986117.
Incorrect Comparison vulnerability in ash-project ash_sql allows a user to pad a string field with tab, newline, carriage-return, or form-feed characters and pass a trimmed uniqueness or equality check in the database that the same expression would fail in memory (or the reverse). string_trim/1 compiles to REGEXP_REPLACE patterns built from an Elixir string in which \s is the escape for a single space (codepoint 32), not a regex whitespace class. The generated SQL therefore removes only literal spaces and leaves tabs, newlines, carriage returns, and form feeds in place, whereas String.trim/1 in Elixir removes them all. Any Ash filter, validation, or identity that relies on string_trim/1 then behaves differently depending on whether Ash pushes the expression down to SQL or evaluates it in memory, so padded input can register a near-duplicate value or slip past a trimmed comparison. This issue affects ash_sql: from 0.1.0 before 0.7.1.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| ash-project | >=0.1.0 <0.7.1, >=dd092ed273dec7bd2194352f24a39229fc8ae68b <1b11b5d8bc5321e2e6acac21594ef08f61986117 | 0.7.1, 1b11b5d8bc5321e2e6acac21594ef08f61986117 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket