# CVE-2023-41923: Weak Password Requirements in Kiloview P1/P2 devices

> Attackers can create accounts with weak passwords on Kiloview P1/P2 devices, potentially leading to unauthorized access.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-q4g5-r7jq-2pcx

## What is CVE-2023-41923?

CVE-2023-41923 is a high-severity vulnerability in Kiloview P1/P2, published on 2 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The user management section of the web application permits the creation of user accounts with excessively weak passwords, including single-character passwords.

Weakness: CWE-521 (Weak Password Requirements)

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


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

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

## Is CVE-2023-41923 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41923 is a high-severity vulnerability in Kiloview P1/P2, published on 2 Jul 2024. 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-2023-41923 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-41923/ (Markdown: https://insights.sbomify.com/CVE-2023-41923/index.md)
```

## Sources

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

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