Saltcorn: SQL Injection via Unparameterized Sync Endpoints (maxLoadedId)
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.4.6, 1.5.6, 1.6.0-beta.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
Saltcorn is an extensible, open source, no-code database application builder. Prior to 1.4.6, 1.5.6, and 1.6.0-beta.5, a SQL injection vulnerability in Saltcorn’s mobile-sync routes allows any authenticated low-privilege user with read access to at least one table to inject arbitrary SQL through sync parameters. This can lead to full database exfiltration, including admin password hashes and configuration secrets, and may also enable database modification or destruction depending on the backend. This vulnerability is fixed in 1.4.6, 1.5.6, and 1.6.0-beta.5.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- saltcorn saltcorn
fixed in 1.4.6; From 1.5.0-beta.0 · fixed in 1.5.6; From 1.6.0-alpha.0 · fixed in 1.6.0-beta.5
- @saltcorn/servernpm
fixed in 1.4.6
- @saltcorn/servernpm
From 1.5.0-beta.0 · fixed in 1.5.6
- @saltcorn/servernpm
From 1.6.0-alpha.0 · fixed in 1.6.0-beta.5