CVE-2022-24073
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 Web Request API in Whale browser before 3.12.129.18 allowed to deny access to the extension store or redirect to any URL when users access the store.
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 · moderate confidenceThe Web Request API in Whale browser prior to version 3.12.129.18 had a permission bypass vulnerability that allowed malicious extensions (or other code using the Web Request API) to block user access to the extension store or redirect users to arbitrary URLs when attempting to access the store. This enables phishing and man-in-the-middle attacks against users.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Identify if Whale browser is installedCheck system for Navercorp Whale browser installation - look in common program directories (e.g., C:\Program Files\Whale or C:\Program Files (x86)\Whale on Windows, or /Applications/Whale.app on macOS)Affected if Whale browser executable is found on the system
-
Locate the Whale browser executableSearch for 'Whale.exe' on Windows or 'Whale' application bundle on macOS in typical installation paths or via system searchAffected if The Whale browser executable exists on the endpoint
-
Determine the installed versionRight-click the Whale executable, select Properties, and view the Version tab (Windows) or get info on the Whale.app bundle (macOS)Affected if The version displayed is less than 3.12.129.18
-
Compare version against affected rangeCompare the discovered version number to the affected range: versions prior to 3.12.129.18 are vulnerableAffected if Installed version is below 3.12.129.18 - the Web Request API permission bypass vulnerability is present
If Whale browser is installed and the version is less than 3.12.129.18, the environment is affected by this CVE.
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. Organizations should identify any Whale browser installations in their environment and ensure the update is applied.
3.12.129.18 or later
- 1. Open Whale browser and navigate to Settings or type 'whale://settings' in the address bar
- 2. Click on 'About Whale' or 'Version' in the settings menu to check the current version number
- 3. If the version is below 3.12.129.18, click 'Update' or 'Check for Updates' to download and install the latest version
- 4. Alternatively, download the latest Whale browser installer from the official Naver Whale website and reinstall to ensure version 3.12.129.18 or later is installed
- 5. After updating, verify the version number displays 3.12.129.18 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24073 — 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-24073 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