How severe is CVE-2022-25219?

CVE-2022-25219 has a CVSS 3.x base score of 8.4, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2022-25219 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-25219?

CVE-2022-25219 primarily affects Phicomm K2 Firmware. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2022-25219?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2022-25219 published?

CVE-2022-25219 was published on 2022-03-10 and last updated on 2026-06-17.

CVE-2022-25219

CVE-2022-25219 is a high-severity vulnerability in Phicomm K2 Firmware with a CVSS 3.x base score of 8.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 8.4)
CVSS v2: 6.9
EPSS exploit prediction: 1% (51st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Phicomm K2 Firmware
Published: 2022-03-10
Last modified: 2026-06-17

Description

A null byte interaction error has been discovered in the code that the telnetd_startup daemon uses to construct a pair of ephemeral passwords that allow a user to spawn a telnet service on the router, and to ensure that the telnet service persists upon reboot. By means of a crafted exchange of UDP packets, an unauthenticated attacker on the local network can leverage this null byte interaction error in such a way as to make those ephemeral passwords predictable (with 1-in-94 odds). Since the attacker must manipulate data processed by the OpenSSL function RSA_public_decrypt(), successful exploitation of this vulnerability depends on the use of an unpadded RSA cipher (CVE-2022-25218).

Frequently asked questions

What is CVE-2022-25219?: A null byte interaction error has been discovered in the code that the telnetd_startup daemon uses to construct a pair of ephemeral passwords that allow a user to spawn a telnet service on the router, and to ensure that the telnet service persists upon reboot. By means of a crafted exchange of UDP packets, an unauthenticated attacker on the local network can leverage this null byte interaction error in such a way as to make those ephemeral passwords predictable (with 1-in-94 odds). Since the attacker must manipulate data processed by the OpenSSL function RSA_public_decrypt(), successful exploitation of this vulnerability depends on the use of an unpadded RSA cipher (CVE-2022-25218).
How severe is CVE-2022-25219?: CVE-2022-25219 has a CVSS 3.x base score of 8.4, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-25219 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-25219?: CVE-2022-25219 primarily affects Phicomm K2 Firmware. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2022-25219?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-25219 published?: CVE-2022-25219 was published on 2022-03-10 and last updated on 2026-06-17.

References

https://www.tenable.com/security/research/tra-2022-01

Affected products (5)

cpe:2.3:o:phicomm:k2_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:phicomm:k3_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:phicomm:k3c_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:phicomm:k2g_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:phicomm:k2p_firmware:*:*:*:*:*:*:*:*

More vulnerabilities in Phicomm K2 Firmware

CVE-2022-25218 — High (CVSS 8.1): The use of the RSA algorithm without OAEP, or any other padding scheme, in telnetd_startup, allows an unauthenticated…
CVE-2023-40796 — High (CVSS 7.8): Phicomm k2 v22.6.529.216 was discovered to contain a command injection vulnerability via the function luci.sys.call.
CVE-2022-48072 — High (CVSS 7.8): Phicomm K2G v22.6.3.20 was discovered to contain a command injection vulnerability via the autoUpTime parameter in the…
CVE-2022-48070 — High (CVSS 7.8): Phicomm K2 v22.6.534.263 was discovered to contain a command injection vulnerability via the autoUpTime parameter in…
CVE-2022-25217 — High (CVSS 7.8): Use of a hard-coded cryptographic key pair by the telnetd_startup service allows an attacker on the local area network…
CVE-2022-48073 — High (CVSS 7.5): Phicomm K2G v22.6.3.20 was discovered to store the root and admin passwords in plaintext.

All CVEs affecting Phicomm K2 Firmware →