LiveActive security incident?Get immediate response
CVE Record

CVE-2018-6849: In the WebRTC component in DuckDuckGo 4.2.0, after visiting a web site that attempts to gather complete cli...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-6849 is a privacy leak in DuckDuckGo 4.2.0 where WebRTC STUN traffic can reveal a user's private IP address after visiting a probing website. This is not described as remote code execution or account compromise, but it can weaken privacy expectations, especially for users relying on VPNs or browser privacy protections.

Executive priority

Treat this as a targeted privacy-risk cleanup, not an emergency breach event. Prioritize users with anonymity, VPN, executive, investigative, or sensitive-network requirements, and verify whether the affected 2018-era version exists in the environment.

Technical view

The CVE describes WebRTC behavior in DuckDuckGo 4.2.0 disclosing a private IP address via a STUN request when a site attempts broad client fingerprinting. The provided sources show public research and exploit references, but no CVSS, CWE, vendor advisory, patch details, or expanded affected-version matrix are included.

Likely exposure

Exposure appears limited to environments using DuckDuckGo 4.2.0 with WebRTC enabled. The source bundle does not confirm other DuckDuckGo versions, platforms, or products. Risk is highest where private IP disclosure undermines privacy, VPN use, network segmentation assumptions, or user anonymity requirements.

Exploitation context

The CVE is not listed as KEV, so active exploitation is not established by the provided evidence. Public exploit and research references exist, indicating the behavior was publicly demonstrable. The issue requires a user to visit a site that probes WebRTC/STUN behavior.

Researcher notes

Evidence is incomplete: severity, CVSS, CWE, patch status, and exact affected platform scope are absent from the bundle. The reliable claim is private IP disclosure through WebRTC STUN in DuckDuckGo 4.2.0 after visiting a probing site.

Mitigation direction

  • Check current DuckDuckGo vendor guidance for affected versions and fixes.
  • Upgrade DuckDuckGo if a vendor-supported fixed version is available.
  • Disable or restrict WebRTC where privacy requirements justify it.
  • Use browser privacy controls that prevent local IP disclosure.
  • Review VPN guidance for WebRTC leak protection.

Validation and detection

  • Identify whether DuckDuckGo 4.2.0 is present in managed endpoints.
  • Confirm whether WebRTC is enabled in affected browser configurations.
  • Test with approved internal privacy-leak validation pages only.
  • Review endpoint telemetry for legacy DuckDuckGo usage.
  • Document whether VPN users depend on browser-level IP privacy.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-6849 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.