# CVE-2017-7911: Code injection in CyberVision Kaa IoT Platform

> Remote attackers can execute arbitrary code on the CyberVision Kaa IoT Platform due to insufficient encapsulation.

- **Severity:** High 8.8 (`CVSS:3.0/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:** 6 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q8vq-355x-4874

## What is CVE-2017-7911?

CVE-2017-7911 is a high-severity code injection vulnerability in CyberVision Kaa IoT Platform, published on 6 May 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Code Injection issue was discovered in CyberVision Kaa IoT Platform, Version 0.7.4. An insufficient-encapsulation vulnerability has been identified, which may allow remote code execution.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-485

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

It affects 1 product.


Products: Cybervision Kaa Iot Platform.

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

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

## Is CVE-2017-7911 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7911 is a high-severity code injection vulnerability in CyberVision Kaa IoT Platform, published on 6 May 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-2017-7911 in the wild and no public exploit code.

Affected product: CyberVision Kaa IoT Platform. 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-7911/ (Markdown: https://insights.sbomify.com/CVE-2017-7911/index.md)
```

## Sources

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

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