# CVE-2015-0897: Other in LINE for Android

> Attackers can intercept traffic and inject scripts to execute code or read data due to lack of SSL/TLS enforcement in the LINE mobile app.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2023
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-9xm2-c28x-g93r

## What is CVE-2015-0897?

CVE-2015-0897 is a medium-severity vulnerability in LINE for Android, published on 31 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-924 (Improper Enforcement of Message Integrity During Transmission in a Communication Channel)

## Which versions are affected by CVE-2015-0897?

It affects 1 product.


Products: Line Line.

## How do I fix CVE-2015-0897?

No fix has been published for CVE-2015-0897 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-0897 being exploited?

There is no known exploitation of CVE-2015-0897 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0897 and fix it if it is affected.

What it is: CVE-2015-0897 is a medium-severity vulnerability in LINE for Android, published on 31 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-0897 in the wild and no public exploit code.

Affected product: LINE for Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-0897/ (Markdown: https://insights.sbomify.com/CVE-2015-0897/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-0897
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-0897
- OSV: https://osv.dev/vulnerability/CVE-2015-0897

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-0897/
Summaries are generated and may contain mistakes; the official description above is the record.