file_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 "same
file_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 "same root name but with a suffix" attack. NOTE: This vulnerability exists because of an incomplete fix for CVE-2016-1242.
- Published
- Apr 4, 2017
- Updated
- Jun 16, 2026
- EPSS
- 1.6% · 74th percentile
- CWE
- CWE-269
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.6%
Affected systems
| 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 tryton3.0.0
- tryton tryton3.0.1
- tryton tryton3.0.10
- tryton tryton3.0.11
- tryton tryton3.0.12
- tryton tryton3.0.13
- tryton tryton3.0.14
- tryton tryton3.0.15
- tryton tryton3.0.16
- tryton tryton3.0.17
- tryton tryton3.0.2
- tryton tryton3.0.3
- tryton tryton3.0.4
- tryton tryton3.0.5
- tryton tryton3.0.6
- tryton tryton3.0.7
- tryton tryton3.0.8
- tryton tryton3.0.9
- tryton tryton3.2.0
- tryton tryton3.2.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (debian). Independent of NVD's CPE analysis and usually ahead of it.
n/a tryton-server before 3.4.0-3+deb8u3
- tryton-server before 3.4.0-3+deb8u3affected
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 4.2.1-2 | 4.2.1-2 |
| Debian:7 | tryton-server | before 2.2.4-1+deb7u4 | 2.2.4-1+deb7u4 |
| Debian:8 | tryton-server | before 3.4.0-3+deb8u3 | 3.4.0-3+deb8u3 |
| PyPI | trytond | from 3 · before 4.2.3 | 4.2.3 |
| PyPI | trytond | from 3.0.0 · up to and including 3.0.17 | — |
| PyPI | trytond | from 3.2.0 · up to and including 3.2.17 | — |
| PyPI | trytond | from 3.4.0 · up to and including 3.4.17 | — |
| PyPI | trytond | from 3.6.0 · up to and including 3.6.16 | — |
| PyPI | trytond | from 3.8.0 · up to and including 3.8.14 | — |
| PyPI | trytond | from 4.0.0 · up to and including 4.0.9 | — |
| PyPI | trytond | from 4.2.0 · before 4.2.3 | 4.2.3 |
Same product
tryton: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-6633The 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.36Monitor
- 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 in23Monitor
- CVE-2016-1241Tryton 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 user21Monitor
- CVE-2020-37014Tryton 5.4 - Persistent Cross-Site Scripting20Monitor
- CVE-2016-1242file_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 authenti18Monitor
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 | 4.2.1-2 · Debian:12 | Package registry (OSV) |
| PyPI:trytond | 4.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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRolerules: - apiGroups: ["*"] resources: ["*"] verbs: ["*"]Fixed
kind: Rolemetadata: namespace: lodos-systemrules: - apiGroups: ["apps"] resources: ["deployments"] verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- hg.tryton.org/trytond?cmd=changeset%3Bnode=472510fdc6f8
- www.debian.org/security/2017/dsa-3826
- www.securityfocus.com/bid/97489
- lists.debian.org/debian-security-announce/2017/msg00084.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.