CVE-2022-24074
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 · uneditedWhale Bridge, a default extension in Whale browser before 3.12.129.18, allowed to receive any SendMessage request from the content script itself that could lead to controlling Whale Bridge if the rendering process compromises.
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 Bridge extension in Naver Whale browser versions before 3.12.129.18 improperly allows SendMessage requests to be received directly from content scripts. This bypasses the intended message passing security model where content scripts should only communicate with background scripts through controlled channels. A compromised rendering process can exploit this to gain full control of the Whale Bridge extension.
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
- 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.
-
Verify Naver Whale browser is installedCheck for Whale browser installation by looking for its executable. Common locations: Windows: %PROGRAMFILES%\Naver\Naver Whale\Application\whale.exe, macOS: /Applications/Naver Whale.app, or check Start Menu/Launchpad for Whale icon.Affected if Naver Whale browser is not found on the system (not applicable)
-
Retrieve installed Whale browser versionOpen Whale browser, navigate to whale://version in the address bar, or go to Settings > About Whale. Record the full version number displayed (e.g., 3.12.129.17 or similar).Affected if Unable to retrieve version information from the browser
-
Compare version against the patched releaseTake the installed version number (e.g., 3.12.129.17) and compare it numerically to 3.12.129.18. The major version is 3, minor is 12, patch is 129, and the last number is the build. If the last number is less than 18, the version is vulnerable.Affected if The installed version is less than 3.12.129.18 (e.g., 3.12.129.17, 3.12.129.0, 3.12.128.5, or any 3.x version below 3.12.129.18)
A user is affected if Naver Whale browser is installed and its version number is lower 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
Upgrade Whale browser to version 3.12.129.18 or later where the Whale Bridge extension properly validates message sources and rejects unauthorized SendMessage requests from content scripts.
3.12.129.18 or later
- 1. Open Whale browser settings or menu
- 2. Navigate to the 'About Whale' section (typically under Menu > Help > About Whale)
- 3. Check the current version number displayed
- 4. If the version is below 3.12.129.18, click the 'Update' or 'Check for Updates' button
- 5. Allow the browser to download and install the update
- 6. Restart Whale browser to complete the update process
- 7. Verify the updated version is 3.12.129.18 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24074 — 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-24074 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