← Back
CVE-2024-22196
SQL Injection in github.com/0xJacky/Nginx-UI (CVE-2024-22196)
Summary
SQL injection in github.com/0xJacky/Nginx-UI (CVE-2024-22196). Confidential information can be exposed externally. Exploitable via `GET /api/dns_credentials`. Mitigation: upgrade to `1.9.10-0.20231219195202-ec93ab05a3ec` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-22196** has been found in github.com/0xJacky/Nginx-UI.
Attackers can target a specific entry point like `GET /api/dns_credentials` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade github.com/0xJacky/Nginx-UI to **1.9.10-0.20231219195202-ec93ab05a3ec** or later.
If unsure, ask your IT team or search "github.com/0xJacky/Nginx-UI CVE-2024-22196" on the vendor's site.
CVE-2024-22196 (github.com/0xJacky/Nginx-UI) — CWE-89 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /api/dns_credentials / `OrderAndPaginate` / `DefaultQuery` / `order`
Patched: `1.9.10-0.20231219195202-ec93ab05a3ec` — 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 github.com/0xJacky/Nginx-UI. Attackers reach the vulnerable code path via `GET /api/dns_credentials` without authentication.
📍 Affected scope
github.com/0xJacky/Nginx-UI — . Attack surface: GET /api/dns_credentials / `OrderAndPaginate` / `DefaultQuery` / `order`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.9.10-0.20231219195202-ec93ab05a3ec**.
🛡️ 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 `GET /api/dns_credentials` requests with malformed payloads or SQL meta-characters. Run `grep -r 'github.com/0xJacky/Nginx-UI' .` 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 'github.com/0xJacky/Nginx-UI' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/0xJacky/Nginx-UI` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /api/dns_credentials' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /api/dns_credentials` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20231219195202-ec93ab05a3ecステージング環境で 1.9.10-0.20231219195202-ec93ab05a3ec に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /api/dns_credentials on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/0xJacky/Nginx-UI
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.9.10-0.20231219195202-ec93ab05a3ec"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-22196
- package https://github.com/0xJacky/nginx-ui
- web https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-h374-mm57-879c
- web https://github.com/0xJacky/nginx-ui/commit/ec93ab05a3ecbb6bcf464d9dca48d74452df8a5b
- web https://github.com/0xjacky/nginx-ui/blob/04bf8ec487f06ab17a9fb7f34a28766e5f53885e/model/model.go#L278-L287
- web https://github.com/0xjacky/nginx-ui/blob/04bf8ec487f06ab17a9fb7f34a28766e5f53885e/model/model.go#L91
- web https://github.com/0xjacky/nginx-ui/blob/04bf8ec487f06ab17a9fb7f34a28766e5f53885e/model/model.go#L99C4
- web https://github.com/advisories/GHSA-h374-mm57-879c