# CVE-2021-33549: UDP Technology/Geutebrück camera devices: Buffer overflow in action parameter leading to RCE

> Attackers can remotely execute arbitrary code on vulnerable IP cameras via a stack-based buffer overflow in the action parameter.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2021
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-w6hr-fq55-vx95

## What is CVE-2021-33549?

CVE-2021-33549 is a high-severity memory corruption vulnerability in Geutebrück E2 Series, published on 13 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple camera devices by UDP Technology, Geutebrück and other vendors are vulnerable to a stack-based buffer overflow condition in the action parameter, which may allow an attacker to remotely execute arbitrary code.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2021-33549?

It affects 16 products.


Products: Geutebrueck G-Cam Ebc-2110 Firmware, Geutebrueck G-Cam Ebc-2111 Firmware, Geutebrueck G-Cam Ebc-2112 Firmware, Geutebrueck G-Cam Efd-2241 Firmware, Geutebrueck G-Cam Efd-2250 Firmware, Geutebrueck G-Cam Efd-2251 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-Cam Ewpc-2271 Firmware, Geutebrueck G-Cam Ewpc-2275 Firmware, Geutebrueck G-Code Eec-2400 Firmware, Geutebrueck G-Code Een-2010 Firmware, Geutebrueck G-Code Een-2040 Firmware.

## How do I fix CVE-2021-33549?

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

## Is CVE-2021-33549 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-33549 exists.

Public exploit code:

- Geutebruck instantrec Remote Command Execution (metasploit)

## Other vulnerabilities in Geutebrück E2 Series

- [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-2021-33549 and fix it if it is affected.

What it is: CVE-2021-33549 is a high-severity memory corruption vulnerability in Geutebrück E2 Series, published on 13 Sep 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-33549 exists.

Affected product: Geutebrück E2 Series. 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-2021-33549/ (Markdown: https://insights.sbomify.com/CVE-2021-33549/index.md)
```

## Sources

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

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