CVE-2014-6633
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe safe_eval function in Tryton's trytond module fails to properly sanitize shell metacharacters in user-supplied input. Authenticated users can inject arbitrary OS commands through the collection.domain field in the webdav module or the formula field in the price_list module by embedding shell metacharacters in these parameters, which are then evaluated by the vulnerable safe_eval function.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.4.0, < 2.4.15>= 2.6.0, < 2.6.14>= 2.8.0, < 2.8.11>= 3.0.0, < 3.0.7>= 3.2.0, < 3.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Tryton versionRun the command to display the installed Tryton version, such as 'trytond --version' or check the version via the package managerAffected if The installed version falls within any of these ranges: 2.4.0 to 2.4.14, 2.6.0 to 2.6.13, 2.8.0 to 2.8.10, 3.0.0 to 3.0.6, or 3.2.0 to 3.2.2
-
Confirm webdav module is loadedInspect the list of enabled modules in the Tryton configuration or check if the webdav module appears in the active module listAffected if The webdav module is enabled and accessible to untrusted or authenticated users, making the collection.domain field exploitable
-
Confirm price_list module is loadedInspect the list of enabled modules in the Tryton configuration or check if the price_list module appears in the active module listAffected if The price_list module is enabled and accessible to untrusted or authenticated users, making the formula field exploitable
A system is affected if it runs a Tryton version within the vulnerable ranges AND has either the webdav or price_list module enabled for users who can supply input to the collection.domain or formula fields.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.4.152.6.142.8.11
Upgrade Tryton to version 2.4.15, 2.6.14, 2.8.11, 3.0.7, 3.2.3 or later. Until patched, disable or restrict access to the webdav and price_list modules for untrusted users.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6633 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-6633 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data