# CVE-2024-36755: Security feature bypass in n/a

> Attackers can perform man-in-the-middle attacks to downgrade firmware or alter download URLs due to missing SSL certificate validation in D-Link routers.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-vpjj-qrvj-m2j4

## What is CVE-2024-36755?

CVE-2024-36755 is a medium-severity vulnerability in n/a, published on 27 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

D-Link DIR-1950 up to v1.11B03 does not validate SSL certificates when requesting the latest firmware version and downloading URL. This can allow attackers to downgrade the firmware version or change the downloading URL via a man-in-the-middle attack.

Weakness: CWE-599 (Missing Validation of OpenSSL Certificate)

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

It affects 1 product.


Products: Dlink Dir-1950 Firmware.

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

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

## Is CVE-2024-36755 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36755 is a medium-severity vulnerability in n/a, published on 27 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36755 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-2024-36755/ (Markdown: https://insights.sbomify.com/CVE-2024-36755/index.md)
```

## Sources

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

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