← Back
CVE-2017-0360
medium
CVSS 5.3
Privilege Escalation in trytond (CVE-2017-0360)
Summary
vulnerability in trytond (CVE-2017-0360). Confidential information can be exposed externally. Mitigation: upgrade to `4.2.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2017-0360** has been found in trytond.
Confidential information can be exposed externally. CVSS score: 5.3/10.
What to do: upgrade trytond to **4.2.3** or later.
If unsure, ask your IT team or search "trytond CVE-2017-0360" on the vendor's site.
CVE-2017-0360 (trytond) — CWE-269 / CVSS v3 5.3
Attack vector: remote (network-reachable) / no user interaction
Patched: `4.2.3` — 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-269) exists in trytond.
📍 Affected scope
trytond — .
🔥 Severity
Severity: Medium (CVSS 5.3/10). Confidential information can be exposed externally
🔧 How to fix
Update to **4.2.3**.
🛡️ 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 'trytond' .` 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 'trytond' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `trytond` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade trytond to 4.2.3ステージング環境で 4.2.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
trytond
[{"type":"ECOSYSTEM","events":[{"introduced":"3"},{"fixed":"4.2.3"}]}]
References
- advisory http://www.debian.org/security/2017/dsa-3826
- advisory https://github.com/advisories/GHSA-7cwg-2575-3546
- web af854a3a-2127-422b-91ae-364da2661108
- web http://www.securityfocus.com/bid/97489
- web https://lists.debian.org/debian-security-announce/2017/msg00084.html
- web http://hg.tryton.org/trytond?cmd=changeset;node=472510fdc6f8