CVE-2023-41919

CVE-2023-41919 is a critical-severity vulnerability in Kiloview P2 Firmware with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-798.

Key facts

Description

Hardcoded credentials are discovered within the application's source code, creating a potential security risk for unauthorized access.

Frequently asked questions

What is CVE-2023-41919?
Hardcoded credentials are discovered within the application's source code, creating a potential security risk for unauthorized access.
How severe is CVE-2023-41919?
CVE-2023-41919 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2023-41919 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-41919?
CVE-2023-41919 primarily affects Kiloview P2 Firmware. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2023-41919?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2023-41919 have an EU (EUVD) identifier?
Yes. CVE-2023-41919 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2023-46396.
When was CVE-2023-41919 published?
CVE-2023-41919 was published on 2024-07-02 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Kiloview P2 Firmware

All CVEs affecting Kiloview P2 Firmware →

Other CWE-798 (Use of Hard-coded Credentials) vulnerabilities

Browse all CWE-798 (Use of Hard-coded Credentials) vulnerabilities →