CVE-2016-7818 json
Untrusted search path vulnerability in Installers for Specification check program (social insurance) Ver.
published 2017-06-09 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-8667
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
Untrusted search path vulnerability in Installers for Specification check program (social insurance) Ver. 9.00 and earlier, TODOKESHO print program Ver. 5.00 and earlier, Device data encryption program Ver. 1.00 and earlier, and TODOKESHO creation program Ver. 15.00 and earlier available prior to October 17, 2016 allows remote attackers to gain privileges via a Trojan horse DLL in an unspecified directory.
Patch / fix
Exploit prediction
0.96% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Japan Pension Service Intstaller for Specification check program(social insurance)
- Japan Pension Service Intstaller for TODOKESHO print program
- Japan Pension Service Intstaller for Device data encryption program
- Japan Pension Service Intstaller for TODOKESHO creation program
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
nenkin.go.jp
/denshibenri/setsumei/20150105-03.html
patch, vendor-advisory
-
nenkin.go.jp
/denshibenri/setsumei/20140630.html
patch, vendor-advisory
-
nenkin.go.jp
/denshibenri/setsumei/0104.html
patch, vendor-advisory
-
nenkin.go.jp
/denshibenri/setsumei/20150415.html#cmscheck
patch, vendor-advisory
-
securityfocus.com
/bid/94616
vdb-entry, third-party-advisory
-
jvn.jp
/en/jp/JVN08868688/index.html
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2016-7818
- NVD CVE-2016-7818
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.