CVE-2022-24815: SQL Injection when creating an application with Reactive SQL backend

Published Apr 11, 2022
·
Updated

JHipster is a development platform to quickly generate, develop, & deploy modern web applications & microservice architectures. SQL Injection vulnerability in entities for applications generated with the option "reactive with Spring WebFlux" enabled and an SQL database using r2dbc. Applications created without "reactive with Spring WebFlux" and applications with NoSQL databases are not affected. Users who have generated a microservice Gateway using the affected version may be impacted as Gateways are reactive by default. Currently, SQL injection is possible in the findAllBy(Pageable pageable, Criteria criteria) method of an entity repository class generated in these applications as the where clause using Criteria for queries are not sanitized and user input is passed on as it is by the criteria. This issue has been patched in v7.8.1. Users unable to upgrade should be careful when combining criterias and conditions as the root of the issue lies in the EntityManager.java class when creating the where clause via Conditions.just(criteria.toString()). just accepts the literal string provided. Criteria's toString method returns a plain string and this combination is vulnerable to sql injection as the string is not sanitized and will contain whatever used passed as input using any plain SQL.

Affected Software

1 affected component
JHipster Generator-jhipster Node.js>=7.0.0<7.8.1

Event History

Apr 11, 2022
CVE Published
via MITRE·07:25 PM
Data Sourced
via MITRE·07:25 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is CVE-2022-24815?

CVE-2022-24815 is a SQL Injection vulnerability in JHipster applications generated with the option "reactive with Spring WebFlux" enabled and an SQL database using r2dbc.

2

How does CVE-2022-24815 affect JHipster applications?

CVE-2022-24815 affects JHipster applications generated with the option "reactive with Spring WebFlux" enabled and an SQL database using r2dbc.

3

What is the severity of CVE-2022-24815?

CVE-2022-24815 has a severity level of 8.1 (High).

4

How can I fix CVE-2022-24815?

To fix CVE-2022-24815, it is recommended to update JHipster to a version that includes the fix.

5

Where can I find more information about CVE-2022-24815?

You can find more information about CVE-2022-24815 in the GitHub advisory: https://github.com/jhipster/generator-jhipster/security/advisories/GHSA-qjmq-8hjr-qcv6.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203