# CVE-2023-41920: Authentication Bypass by Primary Weakness in Kiloview P1/P2 devices


- **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
- **Fix available:** No
- **Published:** 2 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-rw3g-85qv-84cg

## What is CVE-2023-41920?

CVE-2023-41920 is a critical vulnerability in Kiloview P1/P2, published on 2 Jul 2024. 

### Official description

The vulnerability allows attackers access to the root account without having to authenticate. Specifically, if the device is configured with the IP address of 10.10.10.10, the root user is automatically logged in.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

## Which versions are affected by CVE-2023-41920?


## How do I fix CVE-2023-41920?

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

## Is CVE-2023-41920 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41920 and fix it if it is affected.

What it is: CVE-2023-41920 is a critical vulnerability in Kiloview P1/P2, published on 2 Jul 2024. 
Exploitation: There is no known exploitation of CVE-2023-41920 in the wild and no public exploit code.

Affected product: Kiloview P1/P2. 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-2023-41920/ (Markdown: https://insights.sbomify.com/CVE-2023-41920/index.md)
```

## Sources

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

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