# CVE-2021-41503: Auth bypass in n/a

> Malicious LAN users can bypass authentication to compromise camera configuration due to incorrect access control in unsupported devices.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 24 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hmwc-33fh-224c

## What is CVE-2021-41503?

CVE-2021-41503 is a high-severity authentication bypass vulnerability in n/a, published on 24 Sep 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DCS-5000L v1.05 and DCS-932L v2.17 and older are affecged by Incorrect Acess Control. The use of the basic authentication for the devices command interface allows attack vectors that may compromise the cameras configuration and allow malicious users on the LAN to access the device. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2021-41503?

It affects 2 products.


Products: D-Link Dcs-5000l Firmware, Dlink Dcs-932l Firmware.

## How do I fix CVE-2021-41503?

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

## Is CVE-2021-41503 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41503 and fix it if it is affected.

What it is: CVE-2021-41503 is a high-severity authentication bypass vulnerability in n/a, published on 24 Sep 2021. 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-2021-41503 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-2021-41503/ (Markdown: https://insights.sbomify.com/CVE-2021-41503/index.md)
```

## Sources

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

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