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

> A malicious app can read sensitive input data from ATOK, requiring user installation of the attacker's app.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h999-rj96-9q7g

## What is CVE-2012-4016?

CVE-2012-4016 is a medium-severity vulnerability in n/a, published on 28 Sep 2012. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The ATOK application before 1.0.4 for Android allows remote attackers to read the learning information file, and obtain sensitive input-string information, via a crafted application.

Weakness: CWE-264

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

It affects 1 product.


Products: Justsystems Atok.

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

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

## Is CVE-2012-4016 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4738](https://insights.sbomify.com/CVE-2009-4738/): Auth bypass in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4016 is a medium-severity vulnerability in n/a, published on 28 Sep 2012. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-4016 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-4016/ (Markdown: https://insights.sbomify.com/CVE-2012-4016/index.md)
```

## Sources

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

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