logrocket-oauth2-example through 2020-05-27 allows SQL injection via the /auth/register username parameter.
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
| Link | Tags |
|---|---|
| https://github.com/diogosouza/logrocket-oauth2-example | broken link |
| https://archive.ph/PecmD | third party advisory |
| https://blog.logrocket.com/implement-oauth-2-0-node-js/ | product technical description vendor advisory |
| https://archive.ph/VlGDa | third party advisory technical description |
| https://github.com/secoats/cve/tree/master/CVE-2022-38488_sqli_logrocket-oauth2-example | third party advisory exploit |