CVE-2023-29551
High · 8.8CVSS
8.8
EPSS
0.5%
Published
Jun 2, 2023
CISA due date
—
Cloudanix analysis
A problem in the web browser could let attackers run harmful programs on a computer if someone visits a specially crafted website.
- Exploitation
- Requires User Interaction
- Attacker needs
- User Interaction
- Complexity
- High
- Impact
- Full Compromise
- Component
- Application
- Class
- Memory Corruption
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Memory corruption vulnerabilities in the browser engine that may allow arbitrary code execution with sufficient attacker effort.
Why it matters to the business
Attackers could gain control of affected browsers on user devices, enabling theft of sensitive data, installation of malware, or further network compromise; widespread use of the browser increases organizational exposure risk.
How an attack unfolds
An attacker hosts or compromises a webpage containing content that triggers the memory safety bugs; when a user loads the page in a vulnerable browser version, the corruption can be leveraged to execute arbitrary code within the browser process.
How to fix it
Upgrade Firefox to version 112 or later, Firefox for Android to 112 or later, and Focus for Android to 112 or later; enable automatic updates where possible and audit all deployments for outdated instances.
How to confirm the fix worked
Check installed browser versions against the minimum fixed release (112) using about:support or enterprise inventory tools; confirm no vulnerable versions remain in the environment.
Typical attack path
- Identify or create a webpage that triggers memory corruption in the target browser
- Deliver the malicious page via phishing email, compromised website, or malvertising
- Victim loads the page using an affected browser version
- Memory corruption occurs and is chained to achieve code execution
- Attacker payload runs within the browser context to steal data or pivot
How to detect it
Examine browser crash reports, memory dumps, and process logs for unexpected corruption indicators; monitor for unusual network activity or new processes spawned from the browser after visiting unknown sites.
What your security team should do
- Prioritize immediate update of all Firefox, Firefox for Android, and Focus for Android instances to version 112 or newer
- Disable automatic loading of untrusted web content in high-risk environments until patches are applied
- Review browser crash logs and telemetry for signs of memory-related instability
- Educate users on avoiding suspicious links and sites
The record
Memory safety bugs present in Firefox 111. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability affects Firefox for Android < 112, Firefox < 112, and Focus for Android < 112.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Ubuntu:18.04:LTS | firefox | 0 | 112.0+build2-0ubuntu0.18.04.1 |
| Ubuntu:18.04:LTS | mozjs38 | 0 | No fix |
| Ubuntu:18.04:LTS | mozjs52 | 0 | No fix |
| Ubuntu:20.04:LTS | firefox | 0 | 112.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 | mozjs78 | 0 | No fix |
| Ubuntu:22.04:LTS | mozjs91 | 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 |
| openSUSE:Tumbleweed | MozillaFirefox | 0 | 112.0.1-1.1 |
| openSUSE:Tumbleweed | firefox-esr | 0 | 128.5.1-1.1 |
Related vulnerabilities
- CVE-2023-25736 An invalid downcast from `nsHTMLDocument` to `nsIContent` could have lead to undefined… Also affects firefox
- CVE-2023-25733 The return value from `gfx::SourceSurfaceSkia::Map()` wasn't being verified which could… Also affects firefox
- CVE-2023-32210 Documents were incorrectly assuming an ordering of principal objects when ensuring we… Also affects firefox
- CVE-2023-32216 Memory safety bugs present in Firefox 112. Also affects firefox
- CVE-2023-32209 A maliciously crafted favicon could have led to an out of memory crash. Also affects firefox
- CVE-2023-32208 Service workers could reveal script base URL due to dynamic `import()`. Also affects firefox
- CVE-2023-32207 A missing delay in popup notifications could have made it possible for an attacker to… Also affects firefox
- CVE-2023-32205 In multiple cases browser prompts could have been obscured by popups controlled by… Also affects firefox