CVE-2019-10679 json
Thomson Reuters Eikon 4.0.42144 allows all local users to modify the service executable file because of weak %PROGRAMFILES(X86)%\Thomson Re…
published 6y ago modified 4mo ago also EUVD-2019-2475
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
Thomson Reuters Eikon 4.0.42144 allows all local users to modify the service executable file because of weak %PROGRAMFILES(X86)%\Thomson Reuters\Eikon permissions.
Is CVE-2019-10679 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- seclists.org http://seclists.org/fulldisclosure/2020/Aug/19 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/158989/Eikon-Thomson-Reuters-4.0.42144-File-Permissions.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-276 Incorrect Default Permissions
References
-
seclists.org
/fulldisclosure/2020/Aug/19
mailing-list, exploit, third-party-advisory
-
packetstormsecurity.com
/files/158989/Eikon-Thomson-Reuters-4.0.42144-File-Permissions.html
exploit, third-party-advisory, vdb-entry
-
thomsonreuters.com
/en/products-services.html
vendor-advisory
-
sec-consult.com
/en/vulnerability-lab/advisories/index.html
third-party-advisory
-
sec-consult.com
/en/blog/advisories/extensive-file-permissions-on-service-executable-in-eikon-thomson-reuters-cve-2019-10679/
third-party-advisory
Sources
- CVE List CVE-2019-10679
- NVD CVE-2019-10679
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.