CVE-2022-24815: Generator jhipster SQL Injection Vulnerability
HIGHCVE-2022-24815 is a HIGH (CVSS 8.1) sql injection vulnerability (CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) affecting Generator jhipster libraries in the npm ecosystem. The issue involves sql injection when creating an application with reactive sql backend. Remediation is available by upgrading affected packages to version 7.8.1.
CVE-2022-24815 at a Glance
Security Impact
CVSS: 8.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2022-24815
To remediate this vulnerability, upgrade all affected Generator jhipster dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install generator-jhipster@7.8.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls generator-jhipster
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2022-24815, inspect your project dependencies using npm:
npm ls generator-jhipster
Analyze the terminal output to locate any version of Generator jhipster in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.8.1), your application is affected.
Note: The npm ls generator-jhipster command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), where 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. In Generator jhipster, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2022-24815 Affected Generator jhipster Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
generator-jhipster
|
npm |
≥ 7.0.0
< 7.8.1
|
7.8.1
|
References
Frequently Asked Questions
What is CVE-2022-24815?
Which Generator jhipster versions are affected?
What version fixes CVE-2022-24815?
Is generator-jhipster affected?
What is the CVSS score of CVE-2022-24815?
What CWE is associated with CVE-2022-24815?
How can I check npm dependencies for CVE-2022-24815?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-qjmq-8hjr-qcv6",
"modified" : "2022-04-18T22:20:12Z",
"published" : "2022-04-07T15:18:05Z",
"aliases" : [ "CVE-2022-24815" ],
"summary" : "SQL Injection when creating an application with Reactive SQL backend ",
"details" : "### Impact\nSQL 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. \n\nIf you have generated a microservice Gateway using the affected version, you might be impacted as Gateways are reactive by default.\n\nCurrently, 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.\n\n## Impacted applications\n- Monolith and microservice applications with SQL database and reactive with Spring WebFlux combination (other combinations are not affected and the issue is only present when you generate entities)\n- Gateway applications with SQL database (issue will appear only when generating entities)\n\n### Patches\nPatched in v7.8.1\n\nThe `findAllBy(Pageable pageable, Criteria criteria)` method has been removed from the entity repositories and `org.springframework.data.relational.core.query.Criteria` support in the underlying methods has been replaced with `org.springframework.data.relational.core.sql.Condition`. This means you won't be able to do custom filtering in the generated applications.\n\nIf you have existing reactive applications generated by the impacted version, we advise you to audit for use of `Criteria` and take appropriate actions.\n\n### Workarounds\n\nThe problem lies in the `EntityManager.java` class when creating the where clause via `Conditions.just(criteria.toString())`.\n\n`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\n\nSo be careful when combining criterias and conditions. As a workaround we have removed the possibility to pass any user-provided criteria to the `createSelect` method of `EntityManager`.\n\n### Example \n\n```java\nCriteria criteria = Criteria.where(\"name\").is(\"foobar';DROP TABLE example;--\"); // parameter is user provided input\ncriteria.toString(); // --> \"'foobar';DROP TABLE example;--'\"\n```\n\n### References\n[More details in this Issue report](https://github.com/jhipster/generator-jhipster/issues/18269)\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [JHipster issue tracker](https://github.com/jhipster/generator-jhipster/issues)\n",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "generator-jhipster"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "7.0.0"
}, {
"fixed" : "7.8.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/jhipster/generator-jhipster/security/advisories/GHSA-qjmq-8hjr-qcv6"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-24815"
}, {
"type" : "WEB",
"url" : "https://github.com/jhipster/generator-jhipster/issues/18269"
}, {
"type" : "WEB",
"url" : "https://github.com/jhipster/generator-jhipster/commit/c220a210fd7742c53eea72bd5fadbb96220faa98"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/jhipster/generator-jhipster"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-89" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2022-04-07T15:18:05Z",
"nvd_published_at" : "2022-04-11T20:15:00Z"
}
}