dbcve.org
LineApplication · Linecorp

CVE-2019-6010

HIGH · 7.8 CVSS v3.1 Published 2019-09-19
Fix available
A fix is available. Upgrade to 9.15.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Integer overflow vulnerability in LINE(Android) from 4.4.0 to the version before 9.15.1 allows remote attackers to cause a denial of service (DoS) condition or execute arbitrary code via a specially crafted image.

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 confidence

Integer overflow vulnerability in the image processing component of LINE Android app versions 4.4.0 through 9.15.0 allows remote attackers to cause denial of service or potentially execute arbitrary code via specially crafted images sent through the chat application.

MitigationUpdate LINE Android to version 9.15.1 or later to receive the patch. Until then, exercise caution with untrusted image attachments.

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
LineApplication
Affected:>= 4.4.0, < 9.15.1

CVSS 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed LINE app version
    Open Android Settings > Apps > LINE > Version (or open LINE app > Settings > About LINE)
    Affected if Version is 4.4.0 through 9.15.0 (any version >= 4.4.0 and < 9.15.1)
  2. Confirm image processing is active
    Verify the LINE app is used to receive image attachments in chats (this is enabled by default)
    Affected if The app processes incoming images in chat conversations

The environment is affected if LINE Android version is 4.4.0 or higher but lower than 9.15.1, as this version range contains the vulnerable image processing component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 9.15.1 or later
Fixed in 9.15.1
Interim mitigation

Update LINE Android to version 9.15.1 or later to receive the patch. Until then, exercise caution with untrusted image attachments.

Fix this in Line Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-6010 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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