CVE-2014-6633 — tryton
HIGHCVE-2014-6633 is a high-severity (CVSS 8.8) CWE-77 vulnerability in tryton. A fix is available for tryton — see the affected versions and patch details below.
Tryton vulnerable to arbitrary command execution
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2014-6633 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.15pip install --upgrade 'tryton==2.4.15' |
| 🐍PyPI | tryton | ≥ 2.6.0&&< 2.6.14 | 2.6.14pip install --upgrade 'tryton==2.6.14' |
| 🐍PyPI | tryton | ≥ 2.8.0&&< 2.8.11 | 2.8.11pip install --upgrade 'tryton==2.8.11' |
| 🐍PyPI | tryton | ≥ 3.2.0&&< 3.2.3 | 3.2.3pip install --upgrade 'tryton==3.2.3' |
| 🐍PyPI | trytond | ≥ 2.4.0&&< 2.4.15 | 2.4.15pip install --upgrade 'trytond==2.4.15' |
| 🐍PyPI | trytond | ≥ 2.6.0&&< 2.6.14 | 2.6.14pip install --upgrade 'trytond==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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-6633 can be triaged on real exposure rather than presence alone.
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 Security finds CVE-2014-6633 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.