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

> A stack-based buffer overflow in the Netgear Orbi RBR750 firmware allows attackers to execute arbitrary code or cause a denial of service.

- **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:** 8 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-8cc5-fr5w-v23m

## What is CVE-2023-49007?

CVE-2023-49007 is a critical memory corruption vulnerability in Netgear Rbr750 Firmware, published on 8 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Netgear Orbi RBR750 firmware before V7.2.6.21, there is a stack-based buffer overflow in /usr/sbin/httpd.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Netgear Rbr750 Firmware.

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

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

## Is CVE-2023-49007 being exploited?

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

## Other vulnerabilities in Netgear Rbr750 Firmware

- [CVE-2026-0404](https://insights.sbomify.com/CVE-2026-0404/): Insufficient input validation in NETGEAR Orbi routers (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-49007 is a critical memory corruption vulnerability in Netgear Rbr750 Firmware, published on 8 Dec 2023. 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-49007 in the wild and no public exploit code.

Affected product: Netgear Rbr750 Firmware. 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-49007/ (Markdown: https://insights.sbomify.com/CVE-2023-49007/index.md)
```

## Sources

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

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