Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-6432: Vulnerability in Mozilla Firefox

0
High
VulnerabilityCVE-2025-6432cvecve-2025-6432
Published: Tue Jun 24 2025 (06/24/2025, 12:28:03 UTC)
Source: CVE Database V5
Vendor/Project: Mozilla
Product: Firefox

Description

When Multi-Account Containers was enabled, DNS requests could have bypassed a SOCKS proxy when the domain name was invalid or the SOCKS proxy was not responding. This vulnerability affects Firefox < 140 and Thunderbird < 140.

AI-Powered Analysis

AILast updated: 10/31/2025, 05:06:19 UTC

Technical Analysis

CVE-2025-6432 is a vulnerability identified in Mozilla Firefox and Thunderbird prior to version 140 that affects the Multi-Account Containers feature. This feature is designed to isolate browsing contexts for privacy and organizational purposes. The vulnerability arises when DNS requests are made for invalid domain names or when the configured SOCKS proxy is unresponsive. Under these conditions, DNS requests bypass the SOCKS proxy, which is intended to anonymize or secure DNS traffic. This bypass leads to DNS leakage, exposing domain queries directly to the network rather than routing them through the proxy. The vulnerability is classified under CWE-200 (Exposure of Sensitive Information) and has a CVSS v3.1 score of 8.6, indicating high severity. The attack vector is network-based, requiring no privileges or user interaction, making it easier to exploit remotely. The impact primarily affects confidentiality by revealing DNS queries, which can be used to infer user activity or target users for further attacks. Integrity and availability impacts are rated lower but present due to potential proxy failure scenarios. No patches or exploits are currently publicly available, but the vulnerability is published and should be addressed promptly. The issue highlights a flaw in the handling of DNS requests in privacy-enhancing browser features and the importance of robust proxy enforcement mechanisms.

Potential Impact

For European organizations, this vulnerability poses a significant risk to user privacy and data confidentiality. DNS leakage can reveal sensitive information about user browsing habits, potentially exposing corporate or personal data to network observers or malicious actors. This is particularly concerning for organizations that rely on SOCKS proxies for anonymization, geo-restriction circumvention, or secure communications. The exposure could facilitate targeted phishing, surveillance, or data exfiltration attacks. Additionally, organizations in regulated sectors such as finance, healthcare, or government may face compliance issues under GDPR or other privacy regulations if user data is inadvertently exposed. The vulnerability could also undermine trust in privacy tools and browser security, impacting remote workers and users who depend on containerization for separating work and personal browsing. Although no known exploits exist yet, the ease of exploitation and high confidentiality impact warrant urgent attention.

Mitigation Recommendations

1. Apply updates to Mozilla Firefox and Thunderbird to version 140 or later as soon as patches become available to ensure the vulnerability is fixed. 2. Until patches are released, consider disabling the Multi-Account Containers feature to prevent DNS requests from bypassing the SOCKS proxy. 3. Configure network monitoring to detect DNS requests that do not route through the expected proxy infrastructure, enabling early detection of leakage. 4. Review and enforce strict proxy configurations and fallback mechanisms to ensure DNS requests cannot bypass proxies under any failure conditions. 5. Educate users about the risks of using Multi-Account Containers with proxies and encourage reporting of unusual network behavior. 6. For organizations using custom proxy or DNS solutions, validate that these systems correctly handle invalid domain names and proxy failures without leaking DNS queries. 7. Implement DNS over HTTPS (DoH) or DNS over TLS (DoT) where possible to encrypt DNS traffic and reduce exposure. 8. Conduct periodic security assessments of browser configurations and proxy setups to identify and remediate similar weaknesses proactively.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
mozilla
Date Reserved
2025-06-20T14:51:37.854Z
Cvss Version
null
State
PUBLISHED

Threat ID: 685aa0274dc24046c1dc5ab2

Added to database: 6/24/2025, 12:55:03 PM

Last enriched: 10/31/2025, 5:06:19 AM

Last updated: 11/22/2025, 6:06:38 PM

Views: 65

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats