# CVE-2012-4005: Information disclosure in n/a

> Remote attackers can obtain sensitive message information from the LINE Android app by exploiting improper handling of implicit intents via a crafted application.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Aug 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-8734-c552-vc8v

## What is CVE-2012-4005?

CVE-2012-4005 is a medium-severity vulnerability in n/a, published on 7 Aug 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The NHN Japan NAVER LINE application before 2.5.5 for Android does not properly handle implicit intents, which allows remote attackers to obtain sensitive message information via a crafted application.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2012-4005?

It affects 1 product.


Products: Naver Nhn Japan Naver Line.

## How do I fix CVE-2012-4005?

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

## Is CVE-2012-4005 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4005 and fix it if it is affected.

What it is: CVE-2012-4005 is a medium-severity vulnerability in n/a, published on 7 Aug 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-4005 in the wild and no public exploit code.

Affected product: n/a. 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-2012-4005/ (Markdown: https://insights.sbomify.com/CVE-2012-4005/index.md)
```

## Sources

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

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