CVE-2020-9754
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 · uneditedNAVER Whale browser mobile app before 1.10.6.2 allows the attacker to bypass its browser unlock function via incognito mode.
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 confidenceNAVER Whale browser mobile app before version 1.10.6.2 contains a security bypass vulnerability where the browser unlock function can be circumvented through incognito mode, allowing unauthorized access to browser contents without authentication.
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.10.6.2CVSS 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.1/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.
-
Confirm NAVER Whale mobile browser is installedCheck your device for the NAVER Whale browser app - look for the Whale icon (blue whale) in your app list or on your home screenAffected if The app is present on the device
-
Check the installed version numberGo to Settings > Apps > Whale > Version (or on Android, long-press the app icon > App info > Version). On iOS, go to Settings > Whale > VersionAffected if Version is displayed as less than 1.10.6.2 (e.g., 1.10.6.1, 1.10.5.x, etc.)
-
Verify if browser lock is enabledOpen Whale browser, tap the menu (three lines) > Settings > Privacy > check if Lock to open browser or Biometric lock is turned ONAffected if The unlock/lock feature is enabled and the version is below 1.10.6.2
-
Test incognito mode access without authenticationWith lock enabled, close the app completely, reopen it, then immediately try to open an incognito tab (or use the incognito shortcut). Observe if it bypasses the lock screenAffected if Incognito mode opens without requiring authentication while lock is enabled, on versions below 1.10.6.2
You are affected if you have NAVER Whale mobile browser installed with a version below 1.10.6.2 and have the browser lock feature enabled.
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 · scoped1.10.6.2
Update NAVER Whale browser mobile app to version 1.10.6.2 or later to remediate this vulnerability.
1.10.6.2 or later
- Open the Google Play Store (Android) or App Store (iOS) on your mobile device
- Search for "NAVER Whale" or "Whale browser"
- Tap on the NAVER Whale app
- Tap the "Update" button to install version 1.10.6.2 or later
- Ensure the updated version is 1.10.6.2 or higher before using the app
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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-2020-9754 — 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-2020-9754 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