CVE-2014-6633: 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…
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.5% (FIRST EPSS); higher than 85.4% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: tryton-server (Debian:12) 3.2.3-1; tryton-server (Debian:6.0) 1.6.1-2+squeeze2; tryton-server (Debian:7) 2.2.4-1+deb7u2.
Low priority for now. Upgrade to tryton-server (Debian:12) 3.2.3-1; tryton-server (Debian:6.0) 1.6.1-2+squeeze2; tryton-server (Debian:7) 2.2.4-1+deb7u2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 12, 2018
- Updated
- Jun 16, 2026
- EPSS
- 2.5% · 85th percentile
- CWE
- CWE-77
Report tools
Action score
36
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| tryton | tryton | cpe:2.3:a:tryton:tryton |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- tryton tryton2.4.0 and later · before 2.4.15
- tryton tryton2.6.0 and later · before 2.6.14
- tryton tryton2.8.0 and later · before 2.8.11
- tryton tryton3.0.0 and later · before 3.0.7
- tryton tryton3.2.0 and later · before 3.2.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | tryton-server | before 3.2.3-1 | 3.2.3-1 |
| Debian:6.0 | tryton-server | before 1.6.1-2+squeeze2 | 1.6.1-2+squeeze2 |
| Debian:7 | tryton-server | before 2.2.4-1+deb7u2 | 2.2.4-1+deb7u2 |
| PyPI | tryton | from 2.6.0 · before 2.6.14 | 2.6.14 |
| PyPI | tryton | from 2.8.0 · before 2.8.11 | 2.8.11 |
| PyPI | tryton | from 3.2.0 · before 3.2.3 | 3.2.3 |
| PyPI | tryton | before 2.4.15 | 2.4.15 |
| PyPI | trytond | from 2.4.0 · before 2.4.15 | 2.4.15 |
| PyPI | trytond | from 2.6.0 · before 2.6.14 | 2.6.14 |
| PyPI | trytond | from 2.8.0 · before 2.8.11 | 2.8.11 |
| PyPI | trytond | from 3.0.0 · before 3.0.7 | 3.0.7 |
| PyPI | trytond | from 3.2.0 · before 3.2.3 | 3.2.3 |
Same product
tryton: all recordsOther highest-scoring records for the same primary product.
- CVE-2013-4510Directory traversal vulnerability in the client in Tryton 3.0.0, as distributed before 20131104 and earlier, allows remote servers to write…32Monitor
- CVE-2018-19443The client in Tryton 5.x before 5.0.1 tries to make a connection to the bus in cleartext instead of encrypted under certain circumstances…23Monitor
- CVE-2017-0360file_open in Tryton 3.x and 4.x through 4.2.2 allows remote authenticated users with certain permissions to read arbitrary files via a…21Monitor
Published before and after this one in the same product
- ← EarlierCVE-2016-1241Sep 7, 2016 · Tryton 3.x before 3.2.17, 3.4.x before 3.4.14, 3.6.x before 3.6.12, 3.8.x before 3.8.8, and 4.x before 4.0.4 allow remote authenticated…21Monitor
- ← EarlierCVE-2016-1242Sep 7, 2016 · file_open in Tryton before 3.2.17, 3.4.x before 3.4.14, 3.6.x before 3.6.12, 3.8.x before 3.8.8, and 4.x before 4.0.4 allows remote…18Monitor
- Later →CVE-2020-37014Jan 30, 2026 · Tryton 5.4 - Persistent Cross-Site Scripting20Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:tryton-server | 3.2.3-1 · Debian:12 | Package registry (OSV) |
| PyPI:tryton | 2.4.15 | Package registry (OSV) |
| PyPI:tryton | 2.6.14 | Package registry (OSV) |
| PyPI:tryton | 2.8.11 | Package registry (OSV) |
| PyPI:tryton | 3.2.3 | Package registry (OSV) |
| PyPI:trytond | 2.4.15 | Package registry (OSV) |
| PyPI:trytond | 2.6.14 | Package registry (OSV) |
| PyPI:trytond | 2.8.11 | Package registry (OSV) |
| PyPI:trytond | 3.0.7 | Package registry (OSV) |
| PyPI:trytond | 3.2.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')CVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- LDAP InjectionCAPEC-136likelihood: High · High
- Command DelimitersCAPEC-15likelihood: High · High
- IMAP/SMTP Command InjectionCAPEC-183Medium
- Command InjectionCAPEC-248likelihood: Medium · High
- Manipulating Writeable Terminal DevicesCAPEC-40likelihood: High · Very High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Manipulating Writeable Configuration FilesCAPEC-75likelihood: High · Very High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.