Cybersecurity

Google posts Chromium browsers' proof-of-concept exploit code without a fix

Asia / India0 views1 min
Google posts Chromium browsers' proof-of-concept exploit code without a fix

Google accidentally exposed proof-of-concept exploit code for an unpatched Chromium vulnerability affecting Chrome, Edge, Brave, Opera, and other Chromium-based browsers, leaving users at risk of persistent browser hijacking. The flaw, reported by researcher Lyra Rebane in late 2022, remained unresolved for over 42 months and could enable limited botnet activity or DDoS attacks, though Google claims a fix is in development.

Google inadvertently published working exploit code for a critical, unpatched vulnerability in Chromium-based browsers, including Chrome, Microsoft Edge, Brave, Opera, Vivaldi, and Arc. The issue, disclosed in a now-removed Chromium bug tracker post, abuses the Background Fetch API to create persistent browser connections that survive restarts, allowing attackers to hijack sessions for proxy browsing or DDoS attacks if users visit a malicious site. The vulnerability was first reported by security researcher Lyra Rebane in late 2022 and internally classified as high-priority by Google. Despite this, it remained unfixed for over 42 months, with Rebane noting long delays in Chromium security patches. While the exploit does not grant system-level access, researchers warn large-scale abuse could still pose significant risks. Affected browsers rely on Chromium’s Background Fetch feature, while Firefox and Safari are unaffected due to their lack of support for this functionality. The exploit triggers via malicious JavaScript, potentially creating hidden background connections, though some browsers may briefly show suspicious download prompts. Google later deleted the post but confirmed it is working on a patch. There is no evidence of widespread exploitation yet, though the accidental release of exploit code increases the risk of attackers weaponizing the flaw before a fix is deployed. The company has not provided a timeline for resolution.

This content was automatically generated and/or translated by AI. It may contain inaccuracies. Please refer to the original sources for verification.

Comments (0)

Log in to comment.

Loading...