dbcve.org
LineApplication

CVE-2015-0897

MEDIUM · 5.9 CVSS v3.1 Published 2023-10-31
Fix available
A fix is available. Upgrade to after 5.0.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
LINE for Android version 5.0.2 and earlier and LINE for iOS version 5.0.0 and earlier are vulnerable to MITM (man-in-the-middle) attack since the application allows non-SSL/TLS communications. As a result, any API may be invoked from a script injected by a MITM (man-in-the-middle) attacker.

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 confidence

LINE for Android (versions up to 5.0.2) and iOS (versions up to 5.0.0) allow non-SSL/TLS communications, enabling man-in-the-middle attackers to inject malicious scripts and invoke arbitrary APIs.

MitigationEnforce SSL/TLS for all network communications and implement proper certificate validation to prevent MITM attacks.

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:<= 5.0.0<= 5.0.2

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/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 checks

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

  1. Check LINE version on Android
    Open Google Play Store, search for LINE, view the app version information. Or go to Settings > Apps > LINE on the device and check the version.
    Affected if Installed version is 5.0.2 or lower (any version up to and including 5.0.2)
  2. Check LINE version on iOS
    Open App Store, search for LINE, tap on the app to view version details. Or go to Settings > General > iPhone Storage > LINE on the device and check the version.
    Affected if Installed version is 5.0.0 or lower (any version up to and including 5.0.0)
  3. Verify if non-SSL communications are possible
    Use a network proxy tool (such as Burp Suite or Charles Proxy) to intercept network traffic from the LINE app. Attempt to identify any connections using HTTP instead of HTTPS.
    Affected if The app makes any network requests over plain HTTP (non-SSL/TLS) protocol

A user is affected if they have LINE for Android version 5.0.2 or lower, or LINE for iOS version 5.0.0 or lower, and the app is capable of or actively using non-encrypted HTTP connections for communication.

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 a release after 5.0.2
Interim mitigation

Enforce SSL/TLS for all network communications and implement proper certificate validation to prevent MITM attacks.

Fix this in Line Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0897 — 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-2015-0897 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