CVE-2017-0360
No exploitation reported by the sources we read.
- Published2017-04-04
- WeaknessCWE-269
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2017-04-0417:59CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-0360?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-0360?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.0 | = 3.0.0 | no fix published | NVD |
| 3.0 | = 3.0.1 | no fix published | NVD |
| 3.0 | = 3.0.2 | no fix published | NVD |
| 3.0 | = 3.0.3 | no fix published | NVD |
| 3.0 | = 3.0.4 | no fix published | NVD |
| 3.0 | = 3.0.5 | no fix published | NVD |
| 3.0 | = 3.0.6 | no fix published | NVD |
| 3.0 | = 3.0.7 | no fix published | NVD |
| 3.0 | = 3.0.8 | no fix published | NVD |
| 3.0 | = 3.0.9 | no fix published | NVD |
| 3.0 | = 3.0.10 | no fix published | NVD |
| 3.0 | = 3.0.11 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.2 | ≥ 3, < 4.2.3 | 4.2.3 | OSV |
| 4.2 | ≥ 4.2.0, < 4.2.3 | 4.2.3 | OSV |
| 3.0 | ≥ 3.0.0, ≤ 3.0.17 | no fix published | OSV |
| 3.2 | ≥ 3.2.0, ≤ 3.2.17 | no fix published | OSV |
| 3.4 | ≥ 3.4.0, ≤ 3.4.17 | no fix published | OSV |
| 3.6 | ≥ 3.6.0, ≤ 3.6.16 | no fix published | OSV |
| 3.8 | ≥ 3.8.0, ≤ 3.8.14 | no fix published | OSV |
| 4.0 | ≥ 4.0.0, ≤ 4.0.9 | no fix published | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.05.3read 2026-10-23
- NVDCVSS 2.03.5read 2026-10-23
- NVDweakness (CWE)CWE-269read 2026-10-23
- FIRST EPSSEPSS score1.6 %2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
- Published
- 2017-04-04
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-0360?
Is CVE-2017-0360 actively exploited?
What is the CVSS score for CVE-2017-0360?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.