# CVE-2024-31798: Hardcoded credentials in n/a

> Attackers with physical access can retrieve the hardcoded root password to gain full control of GNCC indoor security cameras.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:P/AC:H/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:** 15 Aug 2024
- **Also known as:** GHSA-6g7p-7w92-r3v3

## What is CVE-2024-31798?

CVE-2024-31798 is a medium-severity 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

Identical Hardcoded Root Password for All Devices in GNCC's GC2 Indoor Security Camera 1080P allows an attacker with physical access to retrieve the root password for all similar devices

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

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

It affects 1 product.


Products: Gncchome Gncc C2 Firmware.

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

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

## Is CVE-2024-31798 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-31800](https://insights.sbomify.com/CVE-2024-31800/): Auth bypass in n/a (medium 6.8)
- [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-31798 and fix it if it is affected.

What it is: CVE-2024-31798 is a medium-severity 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: There is no known exploitation of CVE-2024-31798 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-2024-31798/ (Markdown: https://insights.sbomify.com/CVE-2024-31798/index.md)
```

## Sources

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

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