# CVE-2024-31800: Auth bypass in n/a

> An attacker with physical access can bypass authentication via the UART port to gain a privileged command shell on the security camera.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Aug 2024
- **Updated:** 30 Oct 2024
- **Also known as:** GHSA-xw3h-6c4j-mqhw

## What is CVE-2024-31800?

CVE-2024-31800 is a medium-severity authentication bypass vulnerability in n/a, published on 15 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Authentication Bypass in GNCC's GC2 Indoor Security Camera 1080P allows an attacker with physical access to gain a privileged command shell via the UART Debugging Port.

Weakness: CWE-287 (Improper Authentication), CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2024-31800?

It affects 1 product.


Products: Gncchome Gncc C2 Firmware.

## How do I fix CVE-2024-31800?

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

## Is CVE-2024-31800 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31800 exists.

## Other vulnerabilities in n/a

- [CVE-2024-31798](https://insights.sbomify.com/CVE-2024-31798/): Hardcoded credentials in n/a (medium 6.4)
- [CVE-2024-31799](https://insights.sbomify.com/CVE-2024-31799/): Information disclosure in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31800 and fix it if it is affected.

What it is: CVE-2024-31800 is a medium-severity authentication bypass vulnerability in n/a, published on 15 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31800 exists.

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-2024-31800/ (Markdown: https://insights.sbomify.com/CVE-2024-31800/index.md)
```

## Sources

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

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