# CVE-2019-13336: Auth bypass in n/a

> Remote attackers can execute arbitrary commands on the doorbell without authentication via TCP port 81, posing a significant security risk to users of this end-of-life device.

- **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 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6pfv-8w3j-pfrp

## What is CVE-2019-13336?

CVE-2019-13336 is a critical authentication bypass vulnerability in n/a, published on 8 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The dbell Wi-Fi Smart Video Doorbell DB01-S Gen 1 allows remote attackers to launch commands with no authentication verification via TCP port 81, because the loginuse and loginpass parameters to openlock.cgi can have arbitrary values. NOTE: the vendor's position is that this product reached end of life in 2016.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-13336?

It affects 1 product.


Products: Dbell Db01-S Firmware.

## How do I fix CVE-2019-13336?

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

## Is CVE-2019-13336 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13336 and fix it if it is affected.

What it is: CVE-2019-13336 is a critical authentication bypass vulnerability in n/a, published on 8 Oct 2019. 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-2019-13336 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-2019-13336/ (Markdown: https://insights.sbomify.com/CVE-2019-13336/index.md)
```

## Sources

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

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