{"answers":{"affected":"2 open source packages ship an affected version, including typeorm. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-33171 exists.","fix":"Upgrade typeorm to 0.3.0 or later.","what":"CVE-2022-33171 is a critical SQL injection vulnerability in n/a, published on 4 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-33171 and fix it if it is affected.\n\nWhat it is: CVE-2022-33171 is a critical SQL injection vulnerability in n/a, published on 4 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-33171 exists.\n\nAffected packages and fixed versions:\n- typeorm (npm): affected all versions; fixed in 0.3.0\n- typeorm (npm): affected all versions; fixed in 0.3.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-33171/ (Markdown: https://insights.sbomify.com/CVE-2022-33171/index.md)","id":"CVE-2022-33171","markdown":"https://insights.sbomify.com/CVE-2022-33171/index.md","name":"CVE-2022-33171","record":{"aliases":["GHSA-fx4w-v43j-vc45"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"TypeORM library","requires_auth":"none","summary":"Attackers can execute arbitrary SQL commands via crafted FindOneOptions objects in TypeORM, potentially reading or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"typeorm","vendor":"typeorm"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"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","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2025-12-08","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-12-08T10:17:22Z","kind":"github_poc","ref":"https://github.com/open-flaw/CVE-2022-33171","stars":0,"title":"CVE-2022-33171: TypeORM SQL Injection Vulnerability"}],"tier":"weaponised"},"has_fix":true,"headline":"SQL injection in typeORM","id":"CVE-2022-33171","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":2,"n_references":4,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2022-33172"},"packages":[{"ecosystem":"npm","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"typeorm","purl":null,"source":"GHSA-fx4w-v43j-vc45"},{"ecosystem":"npm","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"typeorm","purl":"pkg:npm/typeorm","source":"GHSA-fx4w-v43j-vc45"}],"prev":{"headline":"Hardcoded credentials in Robotic Process Automation","id":"CVE-2022-33169"},"products":["n/a"],"published":"2022-07-04","related":[{"cvss_score":9.8,"headline":"TypeORM vulnerable to MAID and Prototype Pollution","id":"CVE-2020-8158","kev_date_added":null,"published":"2020-09-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can execute arbitrary SQL commands via crafted FindOneOptions objects in TypeORM, potentially reading or modifying database contents.","url":"https://insights.sbomify.com/CVE-2022-33171/"}