update_by_case before 0.1.3 can be vulnerable to sql injection

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0065, the 51st percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 11 Aug 2022. New records show when each source confirmed them.

Sources

• GitHub Advisory Database: GHSA-33wh-w4m7-c6r8
• OSV: GHSA-33wh-w4m7-c6r8
• github.com/camilova/activerecord-update-by-case/security/advisories/GHSA-33wh-w4m7-c6r8
• nvd.nist.gov/vuln/detail/CVE-2022-35956
• github.com/camilova/activerecord-update-by-case
• github.com/camilova/activerecord-update-by-case/releases/tag/v0.1.3-stable
• github.com/rubysec/ruby-advisory-db/blob/master/gems/update_by_case/CVE-2022-35956.yml

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.