Emulator data exfiltration via browser-triggered export
Published May 2, 2024 · Updated Aug 1, 2024
CSRF in Firebase CLI before 13.6.0 allows remote attackers to exfiltrate emulator data through a browser request to localhost. The EmulatorHub export route accepts browser-originated POST requests and exports emulator data to a requested path without rejecting the Origin header. Exploitation requires the emulator suite to be running and a user to visit a malicious site in a browser that permits localhost calls, such as Chrome before 94.
Summary
What happened
CSRF in Firebase CLI before 13.6.0 allows remote attackers to exfiltrate emulator data through a browser request to localhost. The EmulatorHub export route accepts browser-originated POST requests and exports emulator data to a requested path without rejecting the Origin header. Exploitation requires the emulator suite to be running and a user to visit a malicious site in a browser that permits localhost calls, such as Chrome before 94.
The record
- CVE
- CVE-2024-4128
- Published
- May 2, 2024
- Updated
- Aug 1, 2024
- Vendor
- Kreait
- Product
- Firebase Admin SDK for PHP
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- May 2, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record 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=0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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