# CVE-2015-7818: Code injection in n/a

> Local attackers can execute arbitrary JSP code with SYSTEM privileges in IBM/Lenovo Switch Center via the Apache Axis AdminService.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q752-6c9f-vmmc

## What is CVE-2015-7818?

CVE-2015-7818 is a high-severity code injection vulnerability in n/a, published on 12 Nov 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The administration-panel web service in IBM System Networking Switch Center (SNSC) before 7.3.1.5 and Lenovo Switch Center before 8.1.2.0 allows local users to execute arbitrary JSP code with SYSTEM privileges by using the Apache Axis AdminService deployment method to install a .jsp file.

Weakness: CWE-264

## Which versions are affected by CVE-2015-7818?

It affects 2 products.


Products: Ibm System Networking Switch Center, Lenovo Switch Center.

## How do I fix CVE-2015-7818?

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

## Is CVE-2015-7818 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7817](https://insights.sbomify.com/CVE-2015-7817/): Race condition in n/a (high 7.1)
- [CVE-2015-7820](https://insights.sbomify.com/CVE-2015-7820/): Race condition in n/a (high 7.1)
- [CVE-2015-7819](https://insights.sbomify.com/CVE-2015-7819/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-7818 and fix it if it is affected.

What it is: CVE-2015-7818 is a high-severity code injection vulnerability in n/a, published on 12 Nov 2015. 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-2015-7818 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-2015-7818/ (Markdown: https://insights.sbomify.com/CVE-2015-7818/index.md)
```

## Sources

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

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