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

Subscriptions

Vendors Products
Typeorm Subscribe
Typeorm Subscribe

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-fx4w-v43j-vc45 SQL injection in typeORM
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Fri, 27 Feb 2026 02:15:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-03T08:01:20.214Z

Reserved: 2022-06-13T00:00:00.000Z

Link: CVE-2022-33171

cve-icon Vulnrichment

Updated: 2024-08-03T08:01:20.214Z

cve-icon NVD

Status : Modified

Published: 2022-07-04T16:15:08.757

Modified: 2024-11-21T07:07:38.707

Link: CVE-2022-33171

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses