P1/P2: Weak Password Requirements
CVE-2023-41923 is a high-severity weak password requirements vulnerability in P1/P2 from KiloView, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected P1/P2 versions: All through 4.8.2605. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.27% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of P1/P2 you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Kiloview | P1/P2 | All through 4.8.2605 | Not stated |
| Kiloview | p1_4g_video_encoder_firmware | all versions | Not stated |
| Kiloview | p2_4g_video_encoder_firmware | all versions | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N. Scored by CNA (ncsc.nl).
Official description
The user management section of the web application permits the creation of user accounts with excessively weak passwords, including single-character passwords.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Weak Password Requirements
The product does not require that users should have strong passwords.
How developers prevent this class of flaw
- Consider a second authentication factor beyond the password, which prevents the password from being a single point of failure. See CWE-308 for further information.
- Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in P1/P2
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 10.0 Critical severity
- 10.0 Critical severity
Recent Weak Password Requirements vulnerabilities
- 8.8 High severity
- 7.5 High severity
- 7.3 High severity
- 7.1 High severity
- 9.8 Critical severity
- 8.1 High severity
Spotted an error? Tell us.