CVE-2023-41928 Remote server offers deprecated TLS protocol in Kiloview P1/P2 devices
Medium 5.3
Published
Updated
Check this codebase for CVE-2023-41928 and fix it if it is affected.
What it is: CVE-2023-41928 is a medium-severity vulnerability in Kiloview P1/P2, published on 2 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-41928 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-41928/ (Markdown: https://insights.sbomify.com/CVE-2023-41928/index.md)
Kiloview P1/P2 devices accept deprecated TLS protocols, exposing users to cryptographic weaknesses and potential security bypasses.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2023-41928?
CVE-2023-41928 is a medium-severity vulnerability in Kiloview P1/P2, published on 2 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
The device is observed to accept deprecated TLS protocols, increasing the risk of cryptographic weaknesses.
Weakness: CWE-327
Which versions are affected by CVE-2023-41928?
How do I fix CVE-2023-41928?
No fix has been published for CVE-2023-41928 yet. Limit exposure of the affected software until one is available.
Is CVE-2023-41928 being exploited?
There is no known exploitation of CVE-2023-41928 in the wild and no public exploit code.
Sources
Also known as GHSA-ww76-ppx6-58rm.