# CVE-2017-6667: Code injection in Cisco Context Service SDK

> Unauthenticated remote attackers can execute arbitrary code via the dynamic JAR update process in the Cisco Context Service SDK.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r9vq-672r-f8rf

## What is CVE-2017-6667?

CVE-2017-6667 is a critical code injection vulnerability in Cisco Context Service SDK, published on 13 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the update process for the dynamic JAR file of the Cisco Context Service software development kit (SDK) could allow an unauthenticated, remote attacker to execute arbitrary code on the affected device with the privileges of the web server. More Information: CSCvb66730. Known Affected Releases: 2.0.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-6667?

It affects 1 product.


Products: Cisco Context Service Development Kit.

## How do I fix CVE-2017-6667?

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

## Is CVE-2017-6667 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6667 and fix it if it is affected.

What it is: CVE-2017-6667 is a critical code injection vulnerability in Cisco Context Service SDK, published on 13 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6667 in the wild and no public exploit code.

Affected product: Cisco Context Service SDK. 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-2017-6667/ (Markdown: https://insights.sbomify.com/CVE-2017-6667/index.md)
```

## Sources

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

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