** DISPUTED ** The findOne function in TypeORM before 0.3.0 can either be supplied with a string or a FindOneOptions object. When input to the function is a user-controlled parsed JSON object, supplying a crafted FindOneOptions instead of an id string leads to SQL injection. NOTE: the vendor's position is that the user's application is responsible for input validation.
References
Link | Resource |
---|---|
https://github.com/typeorm/typeorm/compare/0.2.45...0.3.0 | Release Notes Third Party Advisory |
https://seclists.org/fulldisclosure/2022/Jun/51 | Exploit Mailing List Third Party Advisory |
http://seclists.org/fulldisclosure/2022/Aug/7 | Mailing List Third Party Advisory |
http://packetstormsecurity.com/files/168096/TypeORM-0.3.7-Information-Disclosure.html | Exploit Third Party Advisory VDB Entry |
Configurations
Information
Published : 2022-07-04 09:15
Updated : 2022-10-18 13:58
NVD link : CVE-2022-33171
Mitre link : CVE-2022-33171
JSON object : View
CWE
CWE-89
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Products Affected
typeorm
- typeorm