CVE-2017-7239

Name: CVE-2017-7239
Creator: NVD / NIST
Published: 2017-04-10T15:59:00.55+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 3.61%

Last modified Jun 17, 2026

CVE-2017-7239 is a vulnerability of currently unknown severity. Ninka before 1.3.2 might allow remote attackers to obtain sensitive information, manipulate license compliance scan results, or cause a denial of service (process hang) via a crafted filename.. EPSS estimates a 3.61% chance of exploitation in the next 30 days.

Description

Ninka before 1.3.2 might allow remote attackers to obtain sensitive information, manipulate license compliance scan results, or cause a denial of service (process hang) via a crafted filename.

Metrics

EPSS Probability

3.61%

88.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-74

Affected Software

Vendor	Product	Versions
Ninka Project	Ninka	<= 1.3.0

References

http://www.openwall.com/lists/oss-security/2017/04/03/3Mailing List, Third Party Advisory
http://www.securityfocus.com/bid/97325Third Party Advisory, VDB Entry
https://github.com/dmgerman/ninka/commit/81f185261c8863c5b84344ee31192870be939fafPatch, Third Party Advisory
http://www.openwall.com/lists/oss-security/2017/04/03/3Mailing List, Third Party Advisory
http://www.securityfocus.com/bid/97325Third Party Advisory, VDB Entry
https://github.com/dmgerman/ninka/commit/81f185261c8863c5b84344ee31192870be939fafPatch, Third Party Advisory

Timeline

Published: Apr 10, 2017
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-7239?

Ninka before 1.3.2 might allow remote attackers to obtain sensitive information, manipulate license compliance scan results, or cause a denial of service (process hang) via a crafted filename.

How severe is CVE-2017-7239?

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

How do I fix CVE-2017-7239?

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.

Are you affected by CVE-2017-7239?

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

Scan your code now

Source: NVD / NIST