# CVE-2021-26611: HejHome IP Camera use of hard-coded credentials vulnerability

> Remote attackers can use hard-coded credentials to fully control the IP camera, including rebooting and resetting it.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6x8r-c56m-hh3p

## What is CVE-2021-26611?

CVE-2021-26611 is a high-severity vulnerability in Goqual GKW-IC052, published on 26 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HejHome GKW-IC052 IP Camera contained a hard-coded credentials vulnerability. This issue allows remote attackers to operate the IP Camera.(reboot, factory reset, snapshot etc..)

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

## Which versions are affected by CVE-2021-26611?

It affects 1 product.


Products: Hej Hejhome Gkw-Ic052 Firmware.

## How do I fix CVE-2021-26611?

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

## Is CVE-2021-26611 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26611 and fix it if it is affected.

What it is: CVE-2021-26611 is a high-severity vulnerability in Goqual GKW-IC052, published on 26 Nov 2021. 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-2021-26611 in the wild and no public exploit code.

Affected product: Goqual GKW-IC052. 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-2021-26611/ (Markdown: https://insights.sbomify.com/CVE-2021-26611/index.md)
```

## Sources

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

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