# CVE-2010-0113: Information disclosure in n/a

> Attackers can read sensitive wipe/lock credentials from device logs via a crafted app, requiring user interaction to install the malicious 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:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Nov 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-jgp9-92r7-vr6g

## What is CVE-2010-0113?

CVE-2010-0113 is a medium-severity vulnerability in n/a, published on 15 Nov 2010. 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 Symantec Norton Mobile Security application 1.0 Beta for Android records setup details, possibly including wipe/lock credentials, in the device logs, which allows user-assisted remote attackers to obtain potentially sensitive information by leveraging the ability of a separate crafted application to read these logs.

Weakness: CWE-255

## Which versions are affected by CVE-2010-0113?

It affects 1 product.


Products: Symantec Mobile Security.

## How do I fix CVE-2010-0113?

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

## Is CVE-2010-0113 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0113 and fix it if it is affected.

What it is: CVE-2010-0113 is a medium-severity vulnerability in n/a, published on 15 Nov 2010. 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-2010-0113 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-2010-0113/ (Markdown: https://insights.sbomify.com/CVE-2010-0113/index.md)
```

## Sources

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

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