← Back
CVE-2023-33175
Vulnerability in toui (CVE-2023-33175)
Summary
vulnerability in toui (CVE-2023-33175). Confidential information can be exposed externally. Exploitable via ``Website.user_vars``. Mitigation: upgrade to `2.4.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2023-33175** has been found in toui.
Attackers can target a specific entry point like ``Website.user_vars`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade toui to **2.4.1** or later.
If unsure, ask your IT team or search "toui CVE-2023-33175" on the vendor's site.
CVE-2023-33175 (toui) — CWE-913 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `Website.user_vars`
Patched: `2.4.1` — 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
**A vulnerability** (CWE-913) exists in toui. Attackers reach the vulnerable code path via ``Website.user_vars`` without authentication.
📍 Affected scope
toui — . Attack surface: `Website.user_vars`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **2.4.1**.
🛡️ 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 'toui' .` 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 'toui' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `toui` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade toui to 2.4.1ステージング環境で 2.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
toui
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.1"},{"fixed":"2.4.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2023-33175
- advisory https://github.com/advisories/GHSA-hh7j-pg39-q563
- package https://github.com/mubarakalmehairbi/ToUI
- package https://pypi.org/project/toui
- web https://github.com/mubarakalmehairbi/ToUI/security/advisories/GHSA-hh7j-pg39-q563
- web https://github.com/mubarakalmehairbi/ToUI/releases/tag/v2.4.1