CVE-2014-6633
HIGHCVE-2014-6633 is a high-severity (CVSS 8.8) CWE-77 vulnerability in tryton. O3 Security confirms whether CVE-2014-6633 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Tryton vulnerable to arbitrary command execution
Blast Radius
tryton🐍tryton🐍tryton🐍tryton🐍trytond🐍trytond🐍trytond🐍trytond+1 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
The safe_eval function in trytond in Tryton before 2.4.15, 2.6.x before 2.6.14, 2.8.x before 2.8.11, 3.0.x before 3.0.7, and 3.2.x before 3.2.3 allows remote authenticated users to execute arbitrary commands via shell metacharacters in (1) the collection.domain in the webdav module or (2) the formula field in the price_list module.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | tryton | all versions | 2.4.15 |
| 🐍PyPI | tryton | ≥ 2.6.0&&< 2.6.14 | 2.6.14 |
| 🐍PyPI | tryton | ≥ 2.8.0&&< 2.8.11 | 2.8.11 |
| 🐍PyPI | tryton | ≥ 3.2.0&&< 3.2.3 | 3.2.3 |
| 🐍PyPI | trytond | ≥ 2.4.0&&< 2.4.15 | 2.4.15 |
| 🐍PyPI | trytond | ≥ 2.6.0&&< 2.6.14 | 2.6.14 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tryton. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update tryton to 2.4.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-6633 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2014-6633 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2014-6633. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2014-6633 in your dependencies?
O3 detects CVE-2014-6633 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.