# CVE-2023-41603: Misconfiguration in n/a

> Attackers can bypass firewall restrictions to access internal services on D-Link R15 routers via IPv6 due to missing traffic rules.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-x24r-vvq6-349r

## What is CVE-2023-41603?

CVE-2023-41603 is a medium-severity vulnerability in n/a, published on 10 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link R15 before v1.08.02 was discovered to contain no firewall restrictions for IPv6 traffic. This allows attackers to arbitrarily access any services running on the device that may be inadvertently listening via IPv6.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Dlink R15 Firmware.

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

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

## Is CVE-2023-41603 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41603 is a medium-severity vulnerability in n/a, published on 10 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-41603 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-41603/ (Markdown: https://insights.sbomify.com/CVE-2023-41603/index.md)
```

## Sources

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

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