Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-46582: CWE-321: Use of Hard-coded Cryptographic Key in ZTE ZXMP M721

0
High
VulnerabilityCVE-2025-46582cvecve-2025-46582cwe-321
Published: Mon Oct 27 2025 (10/27/2025, 08:44:49 UTC)
Source: CVE Database V5
Vendor/Project: ZTE
Product: ZXMP M721

Description

A private key disclosure vulnerability exists in ZTE's ZXMP M721 product. A low-privileged user can bypass authorization checks to view the device's communication private key, resulting in key exposure and impacting communication security.

AI-Powered Analysis

AILast updated: 11/03/2025, 09:25:20 UTC

Technical Analysis

CVE-2025-46582 is a vulnerability identified in the ZTE ZXMP M721, a network device commonly used in telecommunications infrastructure. The core issue is the presence of a hard-coded cryptographic private key within the device's firmware (classified under CWE-321). This key is intended to secure communications handled by the device. However, due to insufficient authorization checks, a low-privileged user can bypass normal access controls and retrieve this private key. The vulnerability affects the specific firmware version ZXMPM721V5.30.020.001P01. The CVSS v3.1 score of 7.7 reflects a high severity, with an attack vector that is network-based (AV:N), requiring low attack complexity (AC:L), and only low privileges (PR:L), but no user interaction (UI:N). The scope is changed (S:C), indicating that exploitation affects resources beyond the initially vulnerable component. The confidentiality impact is high (C:H), as the private key exposure can lead to decryption of sensitive communications or impersonation attacks. Integrity and availability impacts are not directly affected. No public exploits are known yet, but the vulnerability poses a significant risk to communication security. The hard-coded key issue is a fundamental cryptographic design flaw, making mitigation challenging without firmware updates. This vulnerability is particularly concerning for telecom operators and enterprises relying on ZTE ZXMP M721 devices for secure communications, as attackers gaining the private key can intercept or manipulate data streams.

Potential Impact

For European organizations, especially telecom operators and critical infrastructure providers, this vulnerability threatens the confidentiality of communications. Exposure of the private key could allow attackers to decrypt sensitive data, conduct man-in-the-middle attacks, or impersonate legitimate network devices, undermining trust in network security. This could lead to data breaches involving personal data, intellectual property, or government communications, potentially violating GDPR and other regulatory requirements. The disruption or compromise of communication channels could also impact service availability indirectly through targeted attacks leveraging the key exposure. Given the reliance on ZTE equipment in various European countries, the risk extends to national security and critical infrastructure resilience. Organizations may face reputational damage, regulatory penalties, and operational disruptions if the vulnerability is exploited.

Mitigation Recommendations

1. Apply firmware updates or patches from ZTE as soon as they become available to remove or replace the hard-coded cryptographic key. 2. If patches are not yet available, isolate affected ZXMP M721 devices within segmented network zones with strict access controls to limit exposure. 3. Implement strong network monitoring and anomaly detection to identify unauthorized access attempts or unusual key usage patterns. 4. Enforce multi-factor authentication and role-based access controls on device management interfaces to prevent low-privileged users from accessing sensitive functions. 5. Conduct regular security audits and penetration testing focused on cryptographic key management and device authorization mechanisms. 6. Coordinate with ZTE and telecom vendors to verify device configurations and ensure no default or hard-coded keys remain in use. 7. Develop incident response plans specifically addressing cryptographic key compromise scenarios to enable rapid containment and recovery. 8. Consider deploying additional encryption layers at higher network levels to mitigate risks if device-level keys are compromised.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
zte
Date Reserved
2025-04-25T00:28:13.909Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68ff324b8f87cfec3dea7cb9

Added to database: 10/27/2025, 8:50:19 AM

Last enriched: 11/3/2025, 9:25:20 AM

Last updated: 12/14/2025, 10:56:33 AM

Views: 176

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats