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

> An attacker on the local network can intercept base64-encoded credentials transmitted between the baby monitor app and camera, leading to credential theft.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rjhq-673f-g5h2

## What is CVE-2018-18767?

CVE-2018-18767 is a high-severity vulnerability in n/a, published on 20 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in D-Link 'myDlink Baby App' version 2.04.06. Whenever actions are performed from the app (e.g., change camera settings or play lullabies), it communicates directly with the Wi-Fi camera (D-Link 825L firmware 1.08) with the credentials (username and password) in base64 cleartext. An attacker could conduct an MitM attack on the local network and very easily obtain these credentials.

Weakness: CWE-326 (Inadequate Encryption Strength)

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

It affects 2 products.


Products: D-Link Dcs-825l Firmware, Dlink Mydlink Baby Camera Monitor.

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

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

## Is CVE-2018-18767 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18442](https://insights.sbomify.com/CVE-2018-18442/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18767 is a high-severity vulnerability in n/a, published on 20 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-18767 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-18767/ (Markdown: https://insights.sbomify.com/CVE-2018-18767/index.md)
```

## Sources

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

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