# CVE-2019-11014: Other in n/a

> Attackers can spoof camera servers to intercept login credentials and deny service to legitimate cameras in the Eye4 application.

- **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:** 8 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-697w-v97c-p7qr

## What is CVE-2019-11014?

CVE-2019-11014 is a critical vulnerability in n/a, published on 8 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The VStarCam vstc.vscam.client library and vstc.vscam shared object, as used in the Eye4 application (for Android, iOS, and Windows), do not prevent spoofing of the camera server. An attacker can create a fake camera server that listens for the client looking for a camera on the local network. When the camera responds to the client, it responds via the broadcast address, giving all information necessary to impersonate the camera. The attacker then floods the client with responses, causing the original camera to be denied service from the client, and thus causing the client to then communicate exclusively with the attacker's fake camera server. When connecting to the fake camera server, the client sends all details necessary to login to the camera (username and password).

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-11014?

It affects 1 product.


Products: Vstarcam Eye4.

## How do I fix CVE-2019-11014?

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

## Is CVE-2019-11014 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11014 and fix it if it is affected.

What it is: CVE-2019-11014 is a critical vulnerability in n/a, published on 8 Apr 2019. 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-2019-11014 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-2019-11014/ (Markdown: https://insights.sbomify.com/CVE-2019-11014/index.md)
```

## Sources

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

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