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

> Visiting a malicious site in DuckDuckGo browser can leak the user's private IP address via WebRTC STUN requests.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-637h-2rp3-w54w

## What is CVE-2018-6849?

CVE-2018-6849 is a medium-severity vulnerability in n/a, published on 1 Apr 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In the WebRTC component in DuckDuckGo 4.2.0, after visiting a web site that attempts to gather complete client information (such as https://ip.voidsec.com), the browser can disclose a private IP address in a STUN request.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Duckduckgo Duckduckgo.

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

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

## Is CVE-2018-6849 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-6849 exists.

Public exploit code:

- HTTP Client LAN IP Address Gather (metasploit)
- WebRTC - Private IP Leakage (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-44683](https://insights.sbomify.com/CVE-2021-44683/): Other in n/a (high 8.2)
- [CVE-2020-15502](https://insights.sbomify.com/CVE-2020-15502/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6849 is a medium-severity vulnerability in n/a, published on 1 Apr 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-6849 exists.

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-6849/ (Markdown: https://insights.sbomify.com/CVE-2018-6849/index.md)
```

## Sources

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

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