CVE-2023-4579
Low · 3.1CVSS
3.1
EPSS
0.5%
Published
Sep 11, 2023
CISA due date
—
Cloudanix analysis
A browser setting could let an attacker make a fake website appear in the address bar as if it were the real one during searches.
- Exploitation
- Requires User Interaction
- Attacker needs
- User Interaction
- Complexity
- High
- Impact
- Other
- Component
- Application
- Class
- Other
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
A crafted search query that is a syntactically valid URL can be displayed in the address bar as if it were the current navigation target when performed through a user-configured default search engine, enabling visual spoofing of origin.
Why it matters to the business
Users may be misled into interacting with attacker-controlled sites under the false impression they are on a legitimate domain, increasing risk of credential theft or social-engineering success; the issue is limited to browsers where an attacker can influence the default search engine setting.
How an attack unfolds
An attacker first convinces or forces a victim to install a malicious search engine as the browser default, then supplies a search term that is a well-formed attacker URL; the browser renders that URL in the address bar, completing the spoof without further user interaction beyond performing the search.
How to fix it
Upgrade Mozilla Firefox to version 117 or later; verify that enterprise policies or user settings do not override the updated default search engine behavior.
How to confirm the fix worked
Confirm browser version is at least 117; test by setting a search engine whose query returns a well-formed URL and verify the address bar no longer displays the query verbatim as the current location.
Typical attack path
- Attacker distributes or tricks user into adding malicious search engine
- User performs a search using a query string that parses as a valid URL
- Browser address bar displays the search query as the navigated location
- Victim is visually convinced they are on the attacker-chosen site
How to detect it
Review browser configuration logs or preference files for unexpected changes to the default search engine; inspect user-initiated search events that contain URL-like strings in telemetry or history exports.
What your security team should do
- Prioritize deployment of Firefox 117+ across all managed endpoints
- Audit and restrict methods that allow users to change the default search engine
- Include browser version checks in endpoint compliance scans
The record
Search queries in the default search engine could appear to have been the currently navigated URL if the search query itself was a well formed URL. This could have led to a site spoofing another if it had been maliciously set as the default search engine. This vulnerability affects Firefox < 117.
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 | 117.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 | 117.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