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

> Unauthenticated attackers can manipulate firmware updates via the web UI to gain full access to VStarcam IP cameras.

- **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:** 23 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w83r-98jh-fgqf

## What is CVE-2019-12288?

CVE-2019-12288 is a critical missing authorization vulnerability in n/a, published on 23 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in upgrade_htmls.cgi on VStarcam 100T (C7824WIP) KR75.8.53.20 and 200V (C38S) KR203.18.1.20 devices. The web service, network, and account files can be manipulated through a web UI firmware update without any authentication. The attacker can achieve access to the device through a manipulated web UI firmware update.

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

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

It affects 2 products.


Products: Vstarcam C7824iwp Firmware, Vstracm C38s Firmware.

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

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

## Is CVE-2019-12288 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12288 is a critical missing authorization vulnerability in n/a, published on 23 May 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-12288 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-12288/ (Markdown: https://insights.sbomify.com/CVE-2019-12288/index.md)
```

## Sources

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

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