# CVE-2013-2318: Missing authorization in n/a

> Attackers can hijack Twitter accounts by exploiting improper access restrictions in the MovatwiTouch Android application's Content Provider.

- **Severity:** Low 2.6 (`AV:N/AC:H/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:** 6 Jun 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-938p-2whj-rv48

## What is CVE-2013-2318?

CVE-2013-2318 is a low-severity missing authorization vulnerability in n/a, published on 6 Jun 2013. 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 Content Provider in the MovatwiTouch application before 1.793 and MovatwiTouch Paid application before 1.793 for Android does not properly restrict access to authorization information, which allows attackers to hijack Twitter accounts via a crafted application.

Weakness: CWE-264

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

It affects 2 products.


Products: Jig Movatwitouch, Jig Movatwitouch Paid.

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

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

## Is CVE-2013-2318 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2318 is a low-severity missing authorization vulnerability in n/a, published on 6 Jun 2013. 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-2013-2318 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-2318/ (Markdown: https://insights.sbomify.com/CVE-2013-2318/index.md)
```

## Sources

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

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