CVE-2022-24072
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 devtools API in Whale browser before 3.12.129.18 allowed extension developers to inject arbitrary JavaScript into the extension store web page via devtools.inspectedWindow, leading to extensions downloading and uploading when users open the developer tool.
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 Whale browser devtools API (devtools.inspectedWindow) had a cross-site scripting vulnerability that allowed malicious extension developers to inject arbitrary JavaScript into the extension store web page. When users opened developer tools, this allowed unauthorized extension downloads and uploads.
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< 3.12.129.18CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Check if Navercorp Whale browser is installedLook for Whale browser in the system. On Windows, check C:\Program Files\Naver\Whale or C:\Users\%USERNAME%\AppData\Local\Naver\Whale. On macOS, check /Applications/Whale.app.Affected if Whale browser is not present on the system, so the CVE does not apply.
-
Find the installed Whale browser versionOpen Whale browser, click the three-dot menu in the top-right corner, go to Whale menu (on macOS) or Help > About Whale (on Windows), and note the version number displayed.Affected if Unable to determine the version because Whale browser cannot be accessed or is not found.
-
Compare the version against the affected rangeCompare the installed version number (for example, 3.12.129.0 or 3.11.0.0) against the vulnerable range: any version less than 3.12.129.18 is affected. Versions 3.12.129.18 and later are patched.Affected if The installed version is less than 3.12.129.18, meaning the devtools.inspectedWindow API vulnerability is present.
A user is affected if Navercorp Whale browser is installed and the installed version is less than 3.12.129.18.
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 · scoped3.12.129.18
Update Whale browser to version 3.12.129.18 or later to patch the vulnerable devtools API.
Whale browser version 3.12.129.18 or later
- 1. Check the currently installed Whale browser version by navigating to whale://version or through the browser's About menu
- 2. If the installed version is below 3.12.129.18, download the latest Whale browser version from the official website or trusted download source
- 3. Uninstall the current Whale browser installation
- 4. Install the updated Whale browser version 3.12.129.18 or later
- 5. After installation, verify the version by checking whale://version to confirm the patch has been applied
- 6. Restart the browser to ensure all components are updated
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-2022-24072 — 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-2022-24072 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