# CVE-2015-6028: SQL injection in Castle Rock Computing SNMPc before 2015-12-17

> SQL injection in Castle Rock Computing SNMPc allows attackers to read or modify database contents via the sc parameter.

- **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:** 10 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4v47-j6h7-7p73

## What is CVE-2015-6028?

CVE-2015-6028 is a high-severity SQL injection vulnerability in Castle Rock Computing SNMPc before 2015-12-17, published on 10 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Castle Rock Computing SNMPc before 2015-12-17 has SQL injection via the sc parameter.

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

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

It affects 1 product.


Products: Castlerock Snmpc.

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

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

## Is CVE-2015-6028 being exploited?

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

## Other vulnerabilities in Castle Rock Computing SNMPc before 2015-12-17

- [CVE-2015-6027](https://insights.sbomify.com/CVE-2015-6027/): Cross-site scripting in Castle Rock Computing SNMPc before 2015-12-17 (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-6028 is a high-severity SQL injection vulnerability in Castle Rock Computing SNMPc before 2015-12-17, published on 10 Apr 2017. 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-6028 in the wild and no public exploit code.

Affected product: Castle Rock Computing SNMPc before 2015-12-17. 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-6028/ (Markdown: https://insights.sbomify.com/CVE-2015-6028/index.md)
```

## Sources

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

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