CVE-2024-30564: nora-firebase-common · Prototype Pollution
Affects nora-firebase-commonSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubandrei-tatar/nora-firebase-commonpkg:github/andrei-tatar/nora-firebase-commonOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately audit all applications and services to identify usage of nora-firebase-common versions between 1.0.41 and 1.12.2. 2. If possible, upgrade to a patched or newer version of the library once available from the vendor or maintainers. 3. Implement strict input validation and sanitization on the updateState parameter to block malicious scripts. 4. Restrict network access to endpoints exposing the updateStateInternal method using firewalls, VPNs, or IP whitelisting. 5. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block exploitation attempts. 6. Monitor logs and network traffic for unusual activity related to updateState parameter usage. 7. Conduct penetration testing and code reviews focusing on Firebase integration points to identify other potential vulnerabilities. 8. Prepare incident response plans to quickly isolate and remediate affected systems if exploitation is detected. 9. Engage with the library maintainers or community to track patch releases and security advisories.
Description
An issue inandrei-tatar nora-firebase-common between v.1.0.41 and v.1.12.2 allows a remote attacker to execute arbitrary code via a crafted script to the updateState parameter of the updateStateInternal method.