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-45489: n/a

0
Critical
VulnerabilityCVE-2024-45489cvecve-2024-45489
Published: Fri Sep 20 2024 (09/20/2024, 00:00:00 UTC)
Source: CVE Database V5

Description

Arc before 2024-08-26 allows remote code execution in JavaScript boosts. Boosts that run JavaScript cannot be shared by default; however (because of misconfigured Firebase ACLs), it is possible to create or update a boost using another user's ID. This installs the boost in the victim's browser and runs arbitrary Javascript on that browser in a privileged context. NOTE: this is a no-action cloud vulnerability with zero affected users.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 08:13:34 UTC

Technical Analysis

CVE-2024-45489 is a critical remote code execution (RCE) vulnerability identified in Arc browsers released before August 26, 2024. The vulnerability stems from improperly configured Firebase Access Control Lists (ACLs) that govern the sharing and updating of JavaScript boosts—small scripts or extensions that run within the browser context. Normally, JavaScript boosts cannot be shared by default to prevent unauthorized code execution. However, due to the misconfiguration, an attacker can exploit the ACLs to create or update a boost using another user's identifier. This action causes the malicious boost to be installed in the victim's browser and executed with privileged context, allowing arbitrary JavaScript code execution. The attack requires no authentication or user interaction, making it highly exploitable remotely over the network. The vulnerability is classified under CWE-284 (Improper Access Control), highlighting the root cause as insufficient enforcement of access permissions. The CVSS v3.1 base score is 9.8 (critical), with vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, indicating network attack vector, low attack complexity, no privileges or user interaction required, and full impact on confidentiality, integrity, and availability. Despite its severity, the vulnerability is noted as a no-action cloud vulnerability with zero affected users, implying that either the vulnerable configuration is not deployed in production or no exploitation has been observed. No patches or exploits are currently reported, but the risk remains high for any deployment using vulnerable Arc versions with misconfigured Firebase ACLs.

Potential Impact

If exploited, this vulnerability allows attackers to execute arbitrary JavaScript code within the victim's browser with elevated privileges. This can lead to full compromise of the user's browser environment, including theft of sensitive data, session hijacking, installation of persistent malicious scripts, and potentially lateral movement within internal networks if the browser is used for accessing corporate resources. The complete compromise of confidentiality, integrity, and availability of the browser session poses severe risks to individual users and organizations relying on Arc browsers. Given the ease of exploitation (no authentication or user interaction required) and network accessibility, the potential impact is critical. However, the current impact is mitigated by the absence of known affected users or active exploitation. Organizations using Arc browsers in environments where Firebase ACLs are misconfigured are at significant risk if the vulnerability is not addressed promptly.

Mitigation Recommendations

1. Immediately update Arc browsers to versions released after 2024-08-26 once patches become available to eliminate the vulnerability. 2. Review and correct Firebase ACL configurations to ensure that boosts cannot be created or updated using another user's ID, enforcing strict access controls and least privilege principles. 3. Implement monitoring and alerting for unusual boost creation or modification activities within Firebase to detect potential exploitation attempts. 4. Conduct security audits of all JavaScript boosts and extensions deployed in the environment to verify their integrity and origin. 5. Educate users and administrators about the risks of sharing boosts and the importance of secure configuration management. 6. Employ Content Security Policy (CSP) headers and browser security features to limit the impact of arbitrary JavaScript execution if exploitation occurs. 7. Maintain an incident response plan to quickly isolate and remediate compromised browsers or accounts if exploitation is detected.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2024-08-30T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6cedb7ef31ef0b56a42f

Added to database: 2/25/2026, 9:43:09 PM

Last enriched: 2/26/2026, 8:13:34 AM

Last updated: 4/12/2026, 7:51:32 AM

Views: 14

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 more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses