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-2024-13983: Inappropriate implementation in Google Chrome

0
Medium
VulnerabilityCVE-2024-13983cvecve-2024-13983
Published: Fri Nov 14 2025 (11/14/2025, 02:29:55 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

Inappropriate implementation in Lens in Google Chrome on iOS prior to 136.0.7103.59 allowed a remote attacker to perform UI spoofing via a crafted QR code. (Chromium security severity: Low)

AI-Powered Analysis

AILast updated: 11/21/2025, 04:54:50 UTC

Technical Analysis

CVE-2024-13983 is a vulnerability identified in the Lens feature of Google Chrome on iOS platforms before version 136.0.7103.59. The flaw stems from an inappropriate implementation that allows a remote attacker to craft malicious QR codes capable of triggering UI spoofing attacks. UI spoofing here means the attacker can manipulate the browser's interface to display deceptive content, potentially tricking users into divulging sensitive information or performing unintended actions. The vulnerability is classified under CWE-601, which relates to URL redirection and open redirect issues, indicating that the crafted QR codes may redirect or display misleading URLs or content. The CVSS 3.1 base score is 6.3 (medium severity), with an attack vector of network (remote), low attack complexity, no privileges required, but user interaction is necessary (scanning the QR code). The impact affects confidentiality, integrity, and availability at a limited level, as the spoofed UI could mislead users but does not directly compromise system integrity or availability. No known exploits have been reported in the wild, but the potential for phishing or social engineering attacks leveraging this vulnerability exists. The vulnerability was published on November 14, 2025, and affects Chrome on iOS devices, a platform widely used in enterprise and consumer environments. The absence of a patch link suggests that users should update to Chrome version 136.0.7103.59 or later once available. This vulnerability highlights the risks associated with QR code scanning and the importance of secure UI implementations in browser features.

Potential Impact

For European organizations, the primary risk lies in the potential for phishing and social engineering attacks that exploit the UI spoofing vulnerability to deceive users into revealing credentials, installing malware, or performing unauthorized transactions. Since the vulnerability affects Chrome on iOS, organizations with employees or customers using iPhones or iPads with Chrome installed are at risk. The impact on confidentiality is moderate due to possible credential theft or data leakage through spoofed interfaces. Integrity and availability impacts are lower but present, as attackers could mislead users into actions that compromise system integrity or disrupt normal operations. Sectors such as finance, healthcare, and government, which rely heavily on secure user interactions and handle sensitive data, are particularly vulnerable. The requirement for user interaction (scanning a QR code) means that targeted phishing campaigns could be effective, especially in environments where QR codes are commonly used for authentication, payments, or information sharing. The lack of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits over time.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Ensure all iOS devices running Google Chrome are updated to version 136.0.7103.59 or later as soon as the patch is available. 2) Educate users about the risks of scanning QR codes from untrusted or unknown sources, emphasizing caution in corporate environments. 3) Implement mobile device management (MDM) policies to enforce browser updates and restrict installation of unapproved apps or extensions that could exacerbate risks. 4) Monitor network traffic and endpoint logs for unusual redirection patterns or phishing attempts that could indicate exploitation attempts. 5) Encourage the use of alternative secure browsers or QR code scanning apps with enhanced security features until the patch is widely deployed. 6) Conduct phishing simulation exercises to raise awareness about social engineering tactics leveraging QR codes. 7) Collaborate with IT security teams to review and harden browser security settings, including disabling automatic QR code scanning features if possible. These steps go beyond generic advice by focusing on user behavior, device management, and proactive monitoring tailored to the specific nature of this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Chrome
Date Reserved
2025-08-25T21:25:12.075Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69169bdeb9f11918f9cf6127

Added to database: 11/14/2025, 3:02:54 AM

Last enriched: 11/21/2025, 4:54:50 AM

Last updated: 11/22/2025, 3:10:58 PM

Views: 15

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