# CVE-2019-10957: Cross-site scripting in Geutebruck IP Cameras

> Remote authenticated attackers can inject malicious code into event configurations, leading to code execution in legitimate users' browsers.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wfh9-fxc6-p4h7

## What is CVE-2019-10957?

CVE-2019-10957 is a medium-severity cross-site scripting vulnerability in Geutebruck IP Cameras, published on 17 Jan 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Geutebruck IP Cameras G-Code(EEC-2xxx), G-Cam(EBC-21xx/EFD-22xx/ETHC-22xx/EWPC-22xx): All versions 1.12.0.25 and prior may allow a remote authenticated attacker with access to event configuration to store malicious code on the server, which could later be triggered by a legitimate user resulting in code execution within the user’s browser.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 11 products.


Products: Geutebrueck G-Cam Ebc-2110 Firmware, Geutebrueck G-Cam Ebc-2111 Firmware, Geutebrueck G-Cam Efd-2240 Firmware, Geutebrueck G-Cam Efd-2241 Firmware, Geutebrueck G-Cam Efd-2250 Firmware, Geutebrueck G-Cam Ethc-2230 Firmware, Geutebrueck G-Cam Ethc-2239 Firmware, Geutebrueck G-Cam Ethc-2240 Firmware, Geutebrueck G-Cam Ethc-2249 Firmware, Geutebrueck G-Cam Ewpc-2270 Firmware, Geutebrueck G-Code Eec-2400 Firmware.

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

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

## Is CVE-2019-10957 being exploited?

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

## Other vulnerabilities in Geutebruck IP Cameras

- [CVE-2021-33543](https://insights.sbomify.com/CVE-2021-33543/): UDP Technology/Geutebrück camera devices: Authentication Bypass (critical 9.8)
- [CVE-2021-33544](https://insights.sbomify.com/CVE-2021-33544/): UDP Technology/Geutebrück camera devices: command injection leading to RCE (high 7.2)
- [CVE-2021-33545](https://insights.sbomify.com/CVE-2021-33545/): UDP Technology/Geutebrück camera devices: Buffer overflow in counter parameter leading to RCE (high 7.2)
- [CVE-2021-33546](https://insights.sbomify.com/CVE-2021-33546/): UDP Technology/Geutebrück camera devices: Buffer overflow in name parameter leading to RCE (high 7.2)
- [CVE-2021-33547](https://insights.sbomify.com/CVE-2021-33547/): UDP Technology/Geutebrück camera devices: Buffer overflow in profile parameter leading to RCE (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-10957 is a medium-severity cross-site scripting vulnerability in Geutebruck IP Cameras, published on 17 Jan 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-10957 in the wild and no public exploit code.

Affected product: Geutebruck IP Cameras. 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-10957/ (Markdown: https://insights.sbomify.com/CVE-2019-10957/index.md)
```

## Sources

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

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