SQL injection in typeORM
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-33171US | critical9.8 | Exploit | ||
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, su… | ||||
02
references
External citations — patches, advisories, analysis.
- http://packetstormsecurity.com/files/168096/TypeORM-0.3.7-Information-Disclosure.htmlWEB
- http://seclists.org/fulldisclosure/2022/Aug/7WEB
- https://github.com/typeorm/typeorm/compare/0.2.45...0.3.0WEB
- https://nvd.nist.gov/vuln/detail/CVE-2022-33171ADVISORY
- https://seclists.org/fulldisclosure/2022/Jun/51WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan