# CVE-2015-8157: SQL injection in n/a

> Remote authenticated users can execute arbitrary SQL commands in Symantec Data Center Security Server, potentially compromising database integrity and confidentiality.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 8 Jun 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w8c7-26w6-xx7c

## What is CVE-2015-8157?

CVE-2015-8157 is a high-severity SQL injection vulnerability in n/a, published on 8 Jun 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in the Management Server in Symantec Embedded Security: Critical System Protection (SES:CSP) 1.0.x before 1.0 MP5, Embedded Security: Critical System Protection for Controllers and Devices (SES:CSP) 6.5.0 before MP1, Critical System Protection (SCSP) before 5.2.9 MP6, Data Center Security: Server Advanced Server (DCS:SA) 6.x before 6.5 MP1 and 6.6 before MP1, and Data Center Security: Server Advanced Server and Agents (DCS:SA) through 6.6 MP1 allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 5 products.


Products: Broadcom Symantec Critical System Protection, Broadcom Symantec Data Center Security Server, Broadcom Symantec Data Center Security Server and Agents, Broadcom Symantec Embedded Security Critical System Protection, Broadcom Symantec Embedded Security Critical System Protection for Controllers and Devices.

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

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

## Is CVE-2015-8157 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-18374](https://insights.sbomify.com/CVE-2019-18374/): Auth bypass in Critical System Protection (CSP) (critical 9.8)
- [CVE-2014-3440](https://insights.sbomify.com/CVE-2014-3440/): Command injection in n/a (critical 9.0)
- [CVE-2015-8798](https://insights.sbomify.com/CVE-2015-8798/): Path traversal in n/a (high 8.0)
- [CVE-2015-8799](https://insights.sbomify.com/CVE-2015-8799/): Path traversal in n/a (high 7.6)
- [CVE-2013-5016](https://insights.sbomify.com/CVE-2013-5016/): Security feature bypass in n/a (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8157 is a high-severity SQL injection vulnerability in n/a, published on 8 Jun 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-8157 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-8157/ (Markdown: https://insights.sbomify.com/CVE-2015-8157/index.md)
```

## Sources

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

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