UI spoofing via crafted Picture-in-Picture content
Published Oct 15, 2024 · Updated Mar 25, 2025
Inappropriate implementation in Google Chrome before 130.0.6723.58 allows remote attackers to spoof UI via a crafted HTML page. Google identifies PictureInPicture as the affected component but has not published the incorrect operation performed on page content. A target must load attacker-controlled HTML; the bounded impact is deceptive interface rendering, not code execution or service interruption.
Summary
What happened
Inappropriate implementation in Google Chrome before 130.0.6723.58 allows remote attackers to spoof UI via a crafted HTML page. Google identifies PictureInPicture as the affected component but has not published the incorrect operation performed on page content. A target must load attacker-controlled HTML; the bounded impact is deceptive interface rendering, not code execution or service interruption.
The record
- CVE
- CVE-2024-9958
- Published
- Oct 15, 2024
- Updated
- Mar 25, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1036
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 15, 2024CVE publishedPublication date reported by the CVE source.
- Mar 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=130.0.6723.58 <130.0.6723.58
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo