CVE-2018-7635
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 1.0.41.8 displays no URL information but only a title of a web page on the browser's address bar when visiting a blank page, which allows an attacker to display a malicious web page with a fake domain name.
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 1.0.41.8 fails to display the actual URL in the address bar when rendering blank pages, showing only the page title instead. This allows malicious sites to obscure their true origin by displaying a trusted domain's title while the address bar remains blank or shows misleading information, facilitating phishing attacks.
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.0.41.8CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Verify Whale Browser is installedLocate the Whale browser executable (whale.exe) in common installation paths such as C:\Program Files\Naver\Whale or C:\Users\%USERNAME%\AppData\Local\Programs\whale, or check for Whale in the Start Menu programs list.Affected if Whale Browser is not found on the system.
-
Obtain the installed version numberOpen Whale Browser and navigate to whale://version in the address bar, or right-click the whale.exe file in the installation directory, select Properties, and view the Details tab for the version information.Affected if Unable to retrieve version information.
-
Compare version to the affected rangeCompare the installed version to 1.0.41.8. The installed version is considered affected if it is less than 1.0.41.8 (for example, 1.0.41.7, 1.0.40.0, or any earlier version).Affected if The installed version is a release earlier than 1.0.41.8 (for example, any version in the 1.0.40.x series or older).
The environment is affected if Navercorp Whale Browser is installed and the installed version is lower than 1.0.41.8.
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.
From vendor data1.0.41.8
Upgrade Whale Browser to version 1.0.41.8 or later. Users should verify URLs by manually typing addresses or using bookmarks rather than trusting displayed titles.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7635 — 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-2018-7635 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