# CVE-2020-24918: Memory corruption in n/a

> Unauthenticated attackers can execute arbitrary code or cause a crash via a buffer overflow in the RTSP service, affecting devices using this demo library.

- **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:** 30 Apr 2021
- **Updated:** 6 Sep 2024
- **Also known as:** GHSA-537m-c5h3-whvr

## What is CVE-2020-24918?

CVE-2020-24918 is a critical memory corruption vulnerability in n/a, published on 30 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer overflow in the RTSP service of the Ambarella Oryx RTSP Server 2020-01-07 allows an unauthenticated attacker to send a crafted RTSP request, with a long digest authentication header, to execute arbitrary code in parse_authentication_header() in libamprotocol-rtsp.so.1 in rtsp_svc (or cause a crash). This allows remote takeover of a Furbo Dog Camera, for example. NOTE: The vendor states that the RTSP library is used for DEMO only, using it in product is a customer's behavior. Ambarella has emphasized that RTSP is DEMO only library, should NOT be used in product in our document. Because Ambarella's SDK is proprietary, we didn't publish our SDK source code in public network.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2020-24918?

It affects 1 product.


Products: Ambarella Oryx Rtsp Server.

## How do I fix CVE-2020-24918?

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

## Is CVE-2020-24918 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-24918 and fix it if it is affected.

What it is: CVE-2020-24918 is a critical memory corruption vulnerability in n/a, published on 30 Apr 2021. 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-2020-24918 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-2020-24918/ (Markdown: https://insights.sbomify.com/CVE-2020-24918/index.md)
```

## Sources

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

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