CVE-2023-6210
Medium · 6.5CVSS
6.5
EPSS
0.6%
Published
Nov 21, 2023
CISA due date
—
Cloudanix analysis
A browser flaw let secure websites accidentally display unsafe content inside pop-up windows, potentially allowing attackers to slip in harmful material.
- Exploitation
- Requires User Interaction
- Attacker needs
- User Interaction
- Complexity
- Low
- Impact
- Data Tampering
- Component
- Application
- Class
- Authorization Bypass
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
The vulnerability permits a pop-up created from a javascript: URL on an HTTPS page to load blockable insecure HTTP content such as iframes, bypassing mixed-content restrictions.
Why it matters to the business
Attackers could load malicious or unauthorized content into otherwise secure browsing sessions, increasing risk of data exposure or unauthorized actions across user populations.
How an attack unfolds
An attacker hosts a malicious HTTPS page that triggers a javascript: pop-up; the pop-up then loads HTTP-sourced iframes or scripts that would normally be blocked, allowing unauthorized content execution.
How to fix it
Upgrade Mozilla Firefox to version 120 or later.
How to confirm the fix worked
Confirm installed Firefox version is 120 or higher; test that javascript: pop-ups from HTTPS pages no longer load HTTP blockable resources.
Typical attack path
- Host a malicious HTTPS webpage
- Trigger a javascript: URL pop-up from that page
- Load blockable HTTP content such as iframes inside the pop-up
- Execute scripts or exfiltrate data via the unauthorized content
How to detect it
Inspect browser history and mixed-content logs for javascript: initiated pop-ups that loaded HTTP resources; correlate with web traffic showing unexpected insecure loads from secure origins.
What your security team should do
- Upgrade all Firefox deployments to version 120 or newer immediately
- Enforce browser update policies across the environment
- Review web proxy or endpoint logs for mixed-content patterns
The record
When an https: web page created a pop-up from a "javascript:" URL, that pop-up was incorrectly allowed to load blockable content such as iframes from insecure http: URLs This vulnerability affects Firefox < 120.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Ubuntu:18.04:LTS | mozjs38 | 0 | No fix |
| Ubuntu:18.04:LTS | mozjs52 | 0 | No fix |
| Ubuntu:20.04:LTS | firefox | 0 | 120.0+build2-0ubuntu0.20.04.1 |
| Ubuntu:20.04:LTS | mozjs52 | 0 | No fix |
| Ubuntu:20.04:LTS | mozjs68 | 0 | No fix |
| Ubuntu:22.04:LTS | mozjs102 | 0 | No fix |
| Ubuntu:22.04:LTS | mozjs78 | 0 | No fix |
| Ubuntu:22.04:LTS | mozjs91 | 0 | No fix |
| Ubuntu:24.04:LTS | mozjs102 | 0 | No fix |
| Ubuntu:Pro:18.04:LTS | mozjs38 | 0 | No fix |
| Ubuntu:Pro:18.04:LTS | mozjs52 | 0 | No fix |
| Ubuntu:Pro:20.04:LTS | mozjs52 | 0 | No fix |
| Ubuntu:Pro:20.04:LTS | mozjs68 | 0 | No fix |
| Ubuntu:Pro:22.04:LTS | mozjs78 | 0 | No fix |
| Ubuntu:Pro:24.04:LTS | mozjs102 | 0 | No fix |
| openSUSE:Tumbleweed | MozillaFirefox | 0 | 120.0-1.1 |
| openSUSE:Tumbleweed | firefox-esr | 0 | 128.5.1-1.1 |
Related vulnerabilities
- CVE-2025-0243 Memory safety bugs present in Firefox 133, Thunderbird 133, Firefox ESR 128.5, and… Also affects mozjs38
- CVE-2025-0237 The WebChannel API, which is used to transport various information across processes, did… Also affects mozjs38
- CVE-2025-0238 Assuming a controlled failed memory allocation, an attacker could have caused a… Also affects mozjs38
- CVE-2025-0240 Parsing a JavaScript module as JSON could, under some circumstances, cause… Also affects mozjs38
- CVE-2025-0239 When using Alt-Svc, ALPN did not properly validate certificates when the original server… Also affects mozjs38
- CVE-2025-0241 When segmenting specially crafted text, segmentation would corrupt memory leading to a… Also affects mozjs38
- CVE-2025-0242 Memory safety bugs present in Firefox 133, Thunderbird 133, Firefox ESR 115.18, Firefox… Also affects mozjs38
- CVE-2024-11704 A double-free issue could have occurred in `sec_pkcs7_decoder_start_decrypt()` when… Also affects mozjs38