CVE-2022-24075
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 browser before 3.12.129.18 allowed extensions to replace JavaScript files of the HWP viewer website which could access to local HWP files. When the HWP files were opened, the replaced script could read the files.
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 confidenceWhale browser before version 3.12.129.18 contained a vulnerability in its extension system where malicious extensions could replace JavaScript files of the built-in HWP (Hangul Word Processor) viewer website. When users opened local HWP files using the browser's viewer, the replaced script could execute and read the file contents, leading to local file disclosure.
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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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.
-
Confirm Whale browser is installedCheck for Navercorp Whale browser installation on the system. Look for Whale in installed applications or check common installation paths.Affected if Whale browser is installed on the system
-
Identify installed Whale browser versionAccess Whale browser settings or about page to view the version number. Typically found in Settings > About Whale or by navigating to whale://version in the address bar.Affected if The installed version is lower than 3.12.129.18
-
Verify HWP viewer usage or configurationCheck if the built-in HWP viewer feature is enabled or has been used. Look for HWP file handling associations or viewer settings within Whale browser.Affected if HWP viewer feature is enabled or HWP files have been opened in the browser
-
Review installed browser extensionsAccess Whale's extension management page (whale://extensions) to list all installed extensions. Note any untrusted or unnecessary extensions that could potentially contain malicious code.Affected if Extensions with elevated privileges or untrusted origins are installed that could modify built-in viewer scripts
A user is affected if Whale browser version is below 3.12.129.18 and either the HWP viewer feature is in use or extensions with sufficient privileges are present that could exploit the JavaScript replacement vulnerability.
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 obtain the vendor patch. Review installed browser extensions and remove any untrusted or unnecessary extensions as a defense-in-depth measure.
3.12.129.18 or later
- Open Whale browser and navigate to Settings or Menu
- Look for 'Check for updates' or 'About Whale' option
- Update to the latest available version
- Verify the updated version is 3.12.129.18 or later
- Restart the browser if prompted
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24075 — 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-24075 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