CVE-2023-25632
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 Android Mobile Whale browser app before 3.0.1.2 allows the attacker to bypass its browser unlock function via 'Open in Whale' feature.
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 Android Mobile Whale browser app before version 3.0.1.2 contains a security bypass vulnerability in its browser unlock function. The 'Open in Whale' deep link feature can be exploited to access the browser content without requiring authentication, circumventing the privacy lock protection that should restrict access.
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.0.1.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 installedCheck device for Naver Whale Browser app - look for 'Whale' or 'Naver Whale' in installed applicationsAffected if Whale Browser app is present on the device
-
Check installed version numberGo to Settings > Apps > Whale Browser > App info to view the version number, or check via adb: adb shell dumpsys package com.naver.whale | grep versionNameAffected if Version is lower than 3.0.1.2 (e.g., 3.0.1.1, 3.0.0.x, or earlier)
-
Confirm privacy lock is enabledOpen Whale Browser, go to Settings > Privacy > Privacy Lock, verify the lock feature is turned ONAffected if Privacy lock is enabled AND version is below 3.0.1.2 - only then is the bypass relevant
-
Test deep link bypassUse another app to trigger the 'whale://' deep link scheme (e.g., from a webpage or via adb intent) while the browser is locked - observe if content loads without authentication promptAffected if Content loads without requesting authentication when privacy lock is enabled and version is vulnerable
User is affected if Whale Browser version is below 3.0.1.2 AND privacy lock is enabled, allowing unauthenticated access via deep links
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.0.1.2
Update the Whale browser app to version 3.0.1.2 or later, which contains the fix for this unlock bypass vulnerability.
Whale Browser Android version 3.0.1.2
- Open Google Play Store on your Android device
- Search for 'Whale Browser' or 'Naver Whale'
- Locate the Whale Browser app in the search results
- Tap the 'Update' button to install version 3.0.1.2 or later
- Alternatively, navigate to Settings > Apps > Whale Browser > Update
- Verify the installed version is 3.0.1.2 or higher in the app info section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25632 — 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-2023-25632 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