# CVE-2018-17240: Information disclosure in n/a

> Unauthenticated attackers can access /proc/kcore on Netwave IP cameras to steal sensitive network configuration data, including credentials.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2022
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c5c9-f2v8-rfmg

## What is CVE-2018-17240?

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

### Official description

There is a memory dump vulnerability on Netwave IP camera devices at //proc/kcore that allows an unauthenticated attacker to exfiltrate sensitive information from the network configuration (e.g., username and password).

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

## Which versions are affected by CVE-2018-17240?

It affects 2 products.


Products: Netwavepr Indoor Ip Camera Firmware, Netwavepr Outdoor Ip Camera Firmware.

## How do I fix CVE-2018-17240?

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

## Is CVE-2018-17240 being exploited?

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

Public exploit code:

- A tool for retrieving login credentials from Netwave IP cameras using a memory dump vulnerability (CVE-2018-17240) (github_poc): https://github.com/Xewdy444/Netgrave
- Bash exploit for the CVE-2018-17240 (Netwave Cameras Memory Leak) (github_poc): https://github.com/FenrirSec/CVE-2018-17240_exploit
- CVE-2018-17240 (github_poc): https://github.com/BBge/CVE-2018-17240

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17240 and fix it if it is affected.

What it is: CVE-2018-17240 is a high-severity vulnerability in n/a, published on 10 Jun 2022. 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-2018-17240 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-2018-17240/ (Markdown: https://insights.sbomify.com/CVE-2018-17240/index.md)
```

## Sources

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

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