CVE-2021-24030
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe fbgames protocol handler registered as part of Facebook Gameroom does not properly quote arguments passed to the executable. That allows a malicious URL to cause code execution. This issue affects versions prior to v1.26.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe fbgames protocol handler in Facebook Gameroom fails to properly quote arguments passed to the executable when processing URL requests, enabling an attacker to inject and execute arbitrary code via a specially crafted fbgames:// URL.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.26.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate Facebook Gameroom installationSearch for 'Facebook Gameroom' in Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or check Program Files for a folder named 'Facebook Gameroom' containing fbgameroom.exeAffected if Facebook Gameroom is installed on the system
-
Determine installed versionRight-click on fbgameroom.exe in the installation folder, select Properties, and view the File Version in the Details tab. Alternatively, query the registry value DisplayVersion under the uninstall key for Facebook GameroomAffected if The version number shown is lower than 1.26.0 (for example, 1.25.0, 1.24.5, etc.)
-
Check if fbgames protocol handler is registeredOpen Registry Editor and navigate to HKCU\Software\Classes\fbgames (or HKLM\Software\Classes\fbgames) to see if a protocol handler entry exists. Alternatively, run 'reg query HKCU\Software\Classes\fbgames' from command promptAffected if The fbgames key exists and contains a URL Protocol value, indicating the protocol handler is active
User is affected if Facebook Gameroom is installed with a version lower than 1.26.0 AND the fbgames protocol handler is registered on the system
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.26.0
Update Facebook Gameroom to version 1.26.0 or later to obtain the patched protocol handler with proper argument quoting.
v1.26.0 or later
- Upgrade Facebook Gameroom to version 1.26.0 or later by downloading the latest version from the official Facebook Gameroom distribution channel
- Verify the installed version after upgrade by checking the application properties or 'About' section to confirm the version is 1.26.0 or higher
- Test that legitimate fbgames:// URLs still function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-24030 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-24030 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data