# CVE-2023-49236: Memory corruption in n/a

> A stack-based buffer overflow in TRENDnet IP cameras allows attackers to execute arbitrary commands via a crafted RTSP request.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 9 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-j4j9-gr8r-6qx2

## What is CVE-2023-49236?

CVE-2023-49236 is a critical memory corruption vulnerability in n/a, published on 9 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stack-based buffer overflow was discovered on TRENDnet TV-IP1314PI 5.5.3 200714 devices, leading to arbitrary command execution. This occurs because of lack of length validation during an sscanf of a user-entered scale field in the RTSP playback function of davinci.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2023-49236?

It affects 1 product.


Products: Trendnet Tv-Ip1314pi Firmware.

## How do I fix CVE-2023-49236?

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

## Is CVE-2023-49236 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-49235](https://insights.sbomify.com/CVE-2023-49235/): Command injection in n/a (critical 9.8)
- [CVE-2023-49237](https://insights.sbomify.com/CVE-2023-49237/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49236 and fix it if it is affected.

What it is: CVE-2023-49236 is a critical memory corruption vulnerability in n/a, published on 9 Jan 2024. 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-2023-49236 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-2023-49236/ (Markdown: https://insights.sbomify.com/CVE-2023-49236/index.md)
```

## Sources

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

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