CVE-2017-7239

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.

Category

9.8
CVSS
Severity: Critical
CVSS 3.0 •
CVSS 2.0 •
EPSS 2.11% Top 20%
Third-Party Advisory openwall.com Third-Party Advisory securityfocus.com Third-Party Advisory github.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/dmgerman/ninka/commit/81f185261c8863c5b84344ee31192870be939faf third party advisory patch
http://www.openwall.com/lists/oss-security/2017/04/03/3 third party advisory mailing list
http://www.securityfocus.com/bid/97325 vdb entry third party advisory

Frequently Asked Questions

What is the severity of CVE-2017-7239?
CVE-2017-7239 has been scored as a critical severity vulnerability.
How to fix CVE-2017-7239?
To fix CVE-2017-7239, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-7239 being actively exploited in the wild?
It is possible that CVE-2017-7239 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~2% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.