CVE-2024-0748
Medium · 4.3CVSS
4.3
EPSS
0.4%
Published
Jan 23, 2024
CISA due date
—
Cloudanix analysis
Older versions of Firefox could be tricked into showing the wrong website address in the browser, potentially fooling users about where they are.
- Exploitation
- Requires User Interaction
- Attacker needs
- User Interaction
- Complexity
- Low
- Impact
- Data Tampering
- Component
- Application
- Class
- Improper Input Validation
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
A compromised content process can update the document URI, enabling an attacker to set an arbitrary URI in the address bar or browser history.
Why it matters to the business
Users may be misled about the site they are visiting, increasing risk of phishing or other social engineering attacks that erode trust in the browser.
How an attack unfolds
An attacker compromises a content process in an affected Firefox version and then manipulates the document URI to display a spoofed address in the address bar or history.
How to fix it
Upgrade Mozilla Firefox to version 122 or later to address the improper input validation in content processes.
How to confirm the fix worked
Verify the installed Firefox version is 122 or higher and test address bar behavior with crafted content process scenarios in a lab environment.
Typical attack path
- Compromise a content process within Firefox
- Use the compromised process to update the document URI to an attacker-controlled value
- Observe the spoofed URI displayed in the address bar or stored in history
How to detect it
Examine browser process logs and history entries for unexpected URI modifications originating from content processes, though specific artifacts are limited without active exploitation.
What your security team should do
- Update all Firefox deployments to version 122 or newer as soon as possible
- Enforce browser update policies across the organization
- Monitor threat intelligence for any increase in exploitation attempts against this family of issues
The record
A compromised content process could have updated the document URI. This could have allowed an attacker to set an arbitrary URI in the address bar or history. This vulnerability affects Firefox < 122.
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 | 122.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 | 122.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