CVE-2017-0360: 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…
Noroxi assessment
Priority: Monitor (action score 21/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: 1.5% (FIRST EPSS); higher than 75.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. Special conditions such as timing or configuration are required.
- Fixed version: tryton-server (Debian:12) 4.2.1-2; tryton-server (Debian:7) 2.2.4-1+deb7u4; tryton-server (Debian:8) 3.4.0-3+deb8u3.
Low priority for now. Upgrade to tryton-server (Debian:12) 4.2.1-2; tryton-server (Debian:7) 2.2.4-1+deb7u4; tryton-server (Debian:8) 3.4.0-3+deb8u3 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
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.5% · 75th percentile
- CWE
- CWE-269
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.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 |
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
Affected versions · NVD (20)
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
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…23Monitor
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 | 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.
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.
- 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: ClusterRole
rules:
- apiGroups: ["*"]
resources: ["*"]
verbs: ["*"]Fixed
kind: Role
metadata:
namespace: lodos-system
rules:
- 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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.