CVE-2022-41568
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 · uneditedLINE client for iOS before 12.17.0 might be crashed by sharing an invalid shared key of e2ee in group chat.
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 LINE iOS client before version 12.17.0 contains a denial-of-service vulnerability where processing an invalid end-to-end encryption (e2ee) shared key in group chat causes the application to crash. The vulnerability is triggered remotely by receiving a malformed shared key from another group chat participant.
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< 12.17.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Check installed LINE iOS versionOpen the App Store app on the iOS device, search for LINE, and view the version number shown on the app listing. Alternatively, go to iOS Settings > General > iPhone Storage, find LINE, and view the version info.Affected if The displayed version number is lower than 12.17.0
-
Confirm version via LINE app settingsOpen the LINE app, tap the Settings gear icon, then go to Settings > About LINE > Version Info to see the exact version number.Affected if Version shown is less than 12.17.0
-
Assess group chat usageDetermine whether the device uses LINE for group messaging, as the vulnerability is triggered by receiving a malformed end-to-end encryption shared key from another group chat participant.Affected if The user participates in group chats on LINE and the version is below 12.17.0
The user is affected if the installed LINE iOS client version is below 12.17.0 and they participate in group chats where a malformed shared key could be received.
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 · scoped12.17.0
Update LINE iOS client to version 12.17.0 or later. Until updated, avoid opening suspicious group chats with unknown contacts.
12.17.0
- 1. Open the App Store on the iOS device
- 2. Search for 'LINE' or navigate to the installed apps section
- 3. Check the current installed version of LINE
- 4. If the version is below 12.17.0, tap 'Update' to install version 12.17.0 or later
- 5. Alternatively, enable automatic app updates in iOS Settings to ensure future versions are installed promptly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41568 — 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-41568 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