# CVE-2013-0718: Information disclosure in n/a

> Attackers can access sensitive information from the Simeji Android app via local filesystem access due to weak file permissions.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4fqh-x494-wh5j

## What is CVE-2013-0718?

CVE-2013-0718 is a medium-severity vulnerability in n/a, published on 27 Mar 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Simeji application 4.8.1 and earlier for Android uses weak permissions for unspecified files, which allows attackers to obtain sensitive information via an application that accesses the local filesystem.

Weakness: CWE-264

## Which versions are affected by CVE-2013-0718?

It affects 1 product.


Products: Simeji Simeji.

## How do I fix CVE-2013-0718?

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

## Is CVE-2013-0718 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-0718 and fix it if it is affected.

What it is: CVE-2013-0718 is a medium-severity vulnerability in n/a, published on 27 Mar 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0718 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-2013-0718/ (Markdown: https://insights.sbomify.com/CVE-2013-0718/index.md)
```

## Sources

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

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