CVE-2022-38488 — logrocket-oauth2-example through 2020-05-27 allows SQL injection via the /auth/r

logrocket-oauth2-example through 2020-05-27 allows SQL injection via the /auth/register username parameter.

01What is this vulnerability?

logrocket-oauth2-example through 2020-05-27 allows SQL injection via the /auth/register username parameter.

02Affected products

Vendor	Product	Versions
n	a / n/a	n/a

03Active exploitation status

Not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. EPSS is the best forward-looking signal — see the EPSS row above.

04Recommended remediation

• Patch to a fixed version listed in the vendor advisory (see references below).
• Mitigate with WAF rules, network egress filters, or feature flags where the patch is not yet available.
• Hunt historical logs for exploitation indicators — see Detection signatures below.

05Technical details

For the full vendor write-up, exploit chains, and reference implementations, see the references list in section 09.

06Detection signatures

Ask SARA in chat to draft a starting detection for this CVE in your stack of choice.

07Related CVEs

No directly-cited follow-up CVEs in the KB record for this advisory. The references list in section 09 carries the vendor cross-references.

08Timeline

• Published: 2022-12-14T00:00:00.000Z
• Last modified: 2025-04-22T16:00:35.149Z

09References

• github.com — https://github.com/diogosouza/logrocket-oauth2-example
• archive.ph — https://archive.ph/PecmD
• blog.logrocket.com — https://blog.logrocket.com/implement-oauth-2-0-node-js/
• archive.ph — https://archive.ph/VlGDa
• github.com — https://github.com/secoats/cve/tree/master/CVE-2022-38488_sqli_logrocket-oauth2-…