CVE-2017-2231

Name: CVE-2017-2231
Creator: NVD / NIST
Published: 2017-07-07T13:29:01.13+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 1.23%

Last modified Jun 17, 2026

CVE-2017-2231 is a vulnerability of currently unknown severity. Untrusted search path vulnerability in The installer of MLIT DenshiSeikabutsuSakuseiShienKensa system Ver3.02 and earlier, distributed till June 20, 2017, The self-extracting archive including the installer of MLIT DenshiSeikabutsuSakuseiShienKensa system Ver3.02 and earlier, distributed till June 20, 2017 allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.. EPSS estimates a 1.23% chance of exploitation in the next 30 days.

Description

Untrusted search path vulnerability in The installer of MLIT DenshiSeikabutsuSakuseiShienKensa system Ver3.02 and earlier, distributed till June 20, 2017, The self-extracting archive including the installer of MLIT DenshiSeikabutsuSakuseiShienKensa system Ver3.02 and earlier, distributed till June 20, 2017 allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.

Metrics

EPSS Probability

1.23%

65.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-426

Affected Software

Vendor	Product	Versions
Mlit	Denshiseikabutsusakuseishienkensa	<= 3.02

References

http://jvn.jp/en/jp/JVN06337557/index.htmlThird Party Advisory, VDB Entry
http://www.mlit.go.jp/common/001189444.pdfVendor Advisory
http://www.mlit.go.jp/gobuild/gobuild_cals_sysv3.htmlVendor Advisory
http://jvn.jp/en/jp/JVN06337557/index.htmlThird Party Advisory, VDB Entry
http://www.mlit.go.jp/common/001189444.pdfVendor Advisory
http://www.mlit.go.jp/gobuild/gobuild_cals_sysv3.htmlVendor Advisory

Timeline

Published: Jul 7, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-2231?

How severe is CVE-2017-2231?

Severity scoring for CVE-2017-2231 is pending analysis. The EPSS model estimates a 1.23% probability of exploitation in the next 30 days.

How do I fix CVE-2017-2231?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2017

View all 2017CVEs →

Are you affected by CVE-2017-2231?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST