Tryton Information Disclosure Vulnerability
CVE-2017-0360GHSA-7cwg-2575-3546
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI trytond
- Affected
- >= 3.0.0, <= 3.0.17>= 3.2.0, <= 3.2.17>= 3.4.0, <= 3.4.17>= 3.6.0, <= 3.6.16>= 3.8.0, <= 3.8.14>= 4.0.0, <= 4.0.9>= 4.2.0, <= 4.2.2
- Fixed in
- 4.2.3
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-7cwg-2575-3546 lists affected ranges: PyPI trytond >=3.0.0 =3.2.0 =3.4.0 =3.6.0 =3.8.0 =4.0.0 =4.2.0 <4.2.3 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-7cwg-2575-3546 lists affected ranges: PyPI trytond >=3.0.0 =3.2.0 =3.4.0 =3.6.0 =3.8.0 =4.0.0 =4.2.0 <=4.2.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 6.0 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2017-0360: 1.55% estimated exploitation activity in the next 30 days; percentile 75.17 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
fileopen 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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-7cwg-2575-3546
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-7cwg-2575-3546
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2017-0360 Advisory: Tryton Information Disclosure Vulnerability IDs: CVE-2017-0360, GHSA-7cwg-2575-3546 Record: https://patchnext.com/advisories/cve-2017-0360 (revision 3, source checked 26 Oct 2026, 13:27 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.0) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: trytond 4.2.3. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI trytond: affected >= 3.0.0, <= 3.0.17; >= 3.2.0, <= 3.2.17; >= 3.4.0, <= 3.4.17; >= 3.6.0, <= 3.6.16; >= 3.8.0, <= 3.8.14; >= 4.0.0, <= 4.0.9; >= 4.2.0, <= 4.2.2; fixed in 4.2.3 ## Suggested inspection (read-only) - `python -m pip show trytond`: prints the installed version. Run with the environment that serves production active. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on trytond. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-7cwg-2575-3546 (OSV record GHSA-7cwg-2575-3546 lists affected ranges: PyPI trytond >=3.0.0 =3.2.0 =3.4.0 =3.6.0 =3.8.0 =4.0.0 =4.2.0 <4.2.3 (fixed)) - Verified: https://github.com/advisories/GHSA-7cwg-2575-3546 (GitHub-reviewed advisory GHSA-7cwg-2575-3546 lists affected ranges: PyPI trytond >=3.0.0 =3.2.0 =3.4.0 =3.6.0 =3.8.0 =4.0.0 =4.2.0 <=4.2.2) Commands are suggestions: review each one before running it.
Loading voting…