CVE-2022-38488
Logrocket-oauth2-example Project Logrocket-oauth2-example vulnerability
logrocket-oauth2-example through 2020-05-27 allows SQL injection via the /auth/register username parameter.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
Affected products
Logrocket-oauth2-example. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Logrocket-oauth2-example Project Logrocket-oauth2-example runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- blog.logrocket.com/implement-oauth-2-0-node-js/ · Vendor Advisory
- archive.ph/PecmD · Third Party Advisory
- archive.ph/VlGDa · Third Party Advisory
- github.com/secoats/cve/tree/master/CVE-2022-38488_sqli_logrocket-oauth2-example · Exploit
- github.com/diogosouza/logrocket-oauth2-example
- nvd.nist.gov/vuln/detail/CVE-2022-38488
- cve.org/CVERecord?id=CVE-2022-38488
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.