CVE-2022-41797
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 · uneditedImproper authorization in handler for custom URL scheme vulnerability in Lemon8 App for Android versions prior to 3.3.5 and Lemon8 App for iOS versions prior to 3.3.5 allows a remote attacker to lead a user to access an arbitrary website via the vulnerable App. As a result, the user may become a victim of a phishing attack.
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 confidenceThe Lemon8 app for Android and iOS contains an improper authorization vulnerability in its custom URL scheme handler. A remote attacker can craft a malicious link that, when opened by a user, causes the app to redirect to an arbitrary website controlled by the attacker. This enables phishing attacks by tricking users into visiting malicious sites while believing they're interacting with the legitimate app.
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.3.5CVSS 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.
-
Verify Lemon8 is installedCheck your Android device (Settings > Apps) or iOS device (Settings > General > iPhone Storage) for the Lemon8 app presenceAffected if Lemon8 app is found on the device
-
Identify installed version on AndroidOpen Android Settings > Apps > Lemon8 and view the version information under App Info or App DetailsAffected if Version shown is less than 3.3.5 (for example, 3.3.4, 3.3.0, etc.)
-
Identify installed version on iOSOpen iOS Settings > General > iPhone Storage > Lemon8, or view the version in the App Store listing if previously downloadedAffected if Version shown is less than 3.3.5 (for example, 3.3.4, 3.3.0, etc.)
You are affected if the Lemon8 app is installed and its installed version number is lower than 3.3.5.
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.3.5
Update Lemon8 to version 3.3.5 or later on both Android and iOS platforms. Users should avoid clicking untrusted links that open the Lemon8 app until the update is applied.
3.3.5 (for both Android and iOS)
- Open the app store on your device (Google Play Store for Android or Apple App Store for iOS)
- Search for "Lemon8" in the respective app store
- Locate the Lemon8 app and check that the installed version is 3.3.5 or higher
- If a lower version is installed, tap the "Update" button to upgrade to version 3.3.5 or latest available version
- After updating, verify the app version in your device settings to confirm the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation4.0 h
- Testing2.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 $2,528.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41797 — 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-41797 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