# CVE-2019-10661: Hardcoded credentials in n/a

> Attackers can gain root access to Grandstream IP cameras because the root account lacks a password, allowing full device control.

- **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:** 30 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8qh6-379w-p4h2

## What is CVE-2019-10661?

CVE-2019-10661 is a critical vulnerability in n/a, published on 30 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On Grandstream GXV3611IR_HD before 1.0.3.23 devices, the root account lacks a password.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Grandstream Gxv3611ir Hd Firmware.

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

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

## Is CVE-2019-10661 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-10660](https://insights.sbomify.com/CVE-2019-10660/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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