# CVE-2019-12919: Missing authorization in n/a

> An attacker on the local network can access and download video archives from the SD card without authentication due to missing authorization checks.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 20 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qjmc-8jwp-c49h

## What is CVE-2019-12919?

CVE-2019-12919 is a medium-severity missing authorization vulnerability in n/a, published on 20 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On Shenzhen Cylan Clever Dog Smart Camera DOG-2W and DOG-2W-V4 devices, an attacker on the local network has unauthenticated access to the internal SD card via the HTTP service on port 8000. The HTTP web server on the camera allows anyone to view or download the video archive recorded and saved on the external memory card attached to the device.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 2 products.


Products: Cylan Clever Dog Smart Camera Panorama Dog-2w Firmware, Cylan Clever Dog Smart Camera Plus Dog-2w-V4 Firmware.

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

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

## Is CVE-2019-12919 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12919 is a medium-severity missing authorization vulnerability in n/a, published on 20 Jun 2019. 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-2019-12919 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-12919/ (Markdown: https://insights.sbomify.com/CVE-2019-12919/index.md)
```

## Sources

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

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