← Back
GHSA-9ggv-8w38-r7pm
SQL Injection in typeorm (GHSA-9ggv-8w38-r7pm)
Summary
SQL injection in typeorm (GHSA-9ggv-8w38-r7pm). Risk of unauthorized operations or information disclosure. Exploitable via ``UpdateQueryBuilder``. Mitigation: upgrade to `0.3.29` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-9ggv-8w38-r7pm** has been found in typeorm.
Attackers can target a specific entry point like ``UpdateQueryBuilder`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade typeorm to **0.3.29** or later.
If unsure, ask your IT team or search "typeorm GHSA-9ggv-8w38-r7pm" on the vendor's site.
GHSA-9ggv-8w38-r7pm (typeorm) — CWE-89 /
Attack surface: `UpdateQueryBuilder` / `SoftDeleteQueryBuilder` / `addOrderBy` / `order`
Patched: `0.3.29` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SQL injection** (CWE-89) exists in typeorm. Attackers reach the vulnerable code path via ``UpdateQueryBuilder`` without authentication.
📍 Affected scope
typeorm — . Attack surface: `UpdateQueryBuilder` / `SoftDeleteQueryBuilder` / `addOrderBy` / `order`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.3.29**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'typeorm' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'typeorm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `typeorm` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade typeorm to 0.3.29ステージング環境で 0.3.29 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
typeorm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.29"}]}]
References
- web https://github.com/typeorm/typeorm/security/advisories/GHSA-9ggv-8w38-r7pm
- web https://github.com/typeorm/typeorm/commit/1b66c44d0410bdc56a0dcefb46be41867ec0fffc
- web https://github.com/typeorm/typeorm/commit/93eec630630b219b162ba4e0c072afa851697cff
- web https://github.com/advisories/GHSA-9ggv-8w38-r7pm