CVE-2024-4773
High · 7.5CVSS
7.5
EPSS
0.5%
Published
May 14, 2024
CISA due date
—
Cloudanix analysis
A browser bug could let attackers show fake website content with no address shown, tricking people into revealing information.
- Exploitation
- Remote Unauthenticated
- Attacker needs
- None
- Complexity
- Low
- Impact
- Other
- Component
- Application
- Class
- Other
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
The vulnerability allows prior page content to persist in the browser view after a network error during loading, resulting in a blank URL bar that can mask a spoofed site.
Why it matters to the business
Potential for users to be deceived by spoofed websites, increasing risk of phishing attacks and data compromise.
How an attack unfolds
An attacker crafts a scenario where a network error occurs during page load in Firefox, causing the previous legitimate-looking content to remain visible while the URL bar is blank, tricking the user into believing they are on a trusted site.
How to fix it
Upgrade Firefox to version 126 or later.
How to confirm the fix worked
Verify browser version is 126 or higher; test page loads with simulated network errors to ensure content clears and URL updates.
Typical attack path
- Setup a malicious page that triggers network error on load
- Serve content mimicking legitimate site
- Exploit the UI flaw to hide the spoofed nature
How to detect it
Review browser logs or user reports of unexpected blank URL bars; no specific IOCs for exploitation as it is a display flaw.
What your security team should do
- Prioritize updating all Firefox instances to version 126+
- Educate users on verifying URLs
- Monitor for phishing attempts
The record
When a network error occurred during page load, the prior content could have remained in view with a blank URL bar. This could have been used to obfuscate a spoofed web site. This vulnerability affects Firefox < 126.
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 | 126.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 |
| openSUSE:Tumbleweed | MozillaFirefox | 0 | 126.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