# CVE-2017-7458: Null dereference in n/a

> Remote attackers can crash the ntopng network monitoring application by sending an empty field, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4qmq-73jf-8wvj, UBUNTU-CVE-2017-7458

## What is CVE-2017-7458?

CVE-2017-7458 is a high-severity vulnerability in n/a, published on 26 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The NetworkInterface::getHost function in NetworkInterface.cpp in ntopng before 3.0 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via an empty field that should have contained a hostname or IP address.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2017-7458?

It affects 1 product.


Products: Ntop Ntopng.

## How do I fix CVE-2017-7458?

No fix has been published for CVE-2017-7458 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-7458 being exploited?

There is no known exploitation of CVE-2017-7458 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-38968](https://insights.sbomify.com/CVE-2026-38968/): Weak cryptography in n/a (critical 9.8)
- [CVE-2017-5473](https://insights.sbomify.com/CVE-2017-5473/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2018-12520](https://insights.sbomify.com/CVE-2018-12520/): Weak cryptography in n/a (high 8.1)
- [CVE-2017-7459](https://insights.sbomify.com/CVE-2017-7459/): Other in n/a (high 7.5)
- [CVE-2017-7416](https://insights.sbomify.com/CVE-2017-7416/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7458 and fix it if it is affected.

What it is: CVE-2017-7458 is a high-severity vulnerability in n/a, published on 26 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-7458 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-7458/ (Markdown: https://insights.sbomify.com/CVE-2017-7458/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7458
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7458
- OSV: https://osv.dev/vulnerability/CVE-2017-7458

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-7458/
Summaries are generated and may contain mistakes; the official description above is the record.