# CVE-2024-44674: Memory corruption in n/a

> A buffer overflow in the D-Link COVR-2600R router allows remote attackers to execute arbitrary code via a crafted HTTP_REFERER header.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2024
- **Updated:** 7 Oct 2024
- **Also known as:** GHSA-9wcc-fp9g-mcjc

## What is CVE-2024-44674?

CVE-2024-44674 is a medium-severity memory corruption vulnerability in n/a, published on 7 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

D-Link COVR-2600R FW101b05 is vulnerable to Buffer Overflow. In the function sub_24E28, the HTTP_REFERER is obtained through an environment variable, and this field is controllable, allowing it to be used as the value for src.

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

## Which versions are affected by CVE-2024-44674?

It affects 1 product.


Products: Dlink Covr-2600r Firmware.

## How do I fix CVE-2024-44674?

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

## Is CVE-2024-44674 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-20432](https://insights.sbomify.com/CVE-2018-20432/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-44674 and fix it if it is affected.

What it is: CVE-2024-44674 is a medium-severity memory corruption vulnerability in n/a, published on 7 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-44674 exists.

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-2024-44674/ (Markdown: https://insights.sbomify.com/CVE-2024-44674/index.md)
```

## Sources

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

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