# CVE-2013-3315: Privilege escalation in n/a

> Authenticated users can escalate privileges to administrator role due to improper access verification in TIBCO Silver Mobile server.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 May 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-7ggp-328x-c7wp

## What is CVE-2013-3315?

CVE-2013-3315 is a medium-severity vulnerability in n/a, published on 31 May 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The server in TIBCO Silver Mobile 1.1.0 does not properly verify access to the administrator role before executing a command, which allows authenticated users to gain privileges via unspecified vectors.

Weakness: CWE-264

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

It affects 1 product.


Products: Tibco Silver Mobile.

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

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

## Is CVE-2013-3315 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3315 is a medium-severity vulnerability in n/a, published on 31 May 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-3315 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-3315/ (Markdown: https://insights.sbomify.com/CVE-2013-3315/index.md)
```

## Sources

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

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