dbcve.org
Zxun EpdgApplication · Zte

CVE-2024-22064

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 5.20.20 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ZTE ZXUN-ePDG product, which serves as the network node of the VoWifi system, under by default configuration, uses a set of non-unique cryptographic keys during establishing a secure connection(IKE) with the mobile devices connecting over the internet . If the set of keys are leaked or cracked, the user session informations using the keys may be leaked.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The ZTE ZXUN-ePDG VoWifi network node uses non-unique/static cryptographic keys during IKE (IPsec Key Exchange) secure connection establishment by default. If these keys are compromised through leakage or cryptographic attacks, an attacker could decrypt all user sessions that used those keys, resulting in confidentiality breach of user session information.

MitigationReplace default/static cryptographic keys with unique, properly generated per-session keys following IKE best practices. Implement proper key management, rotation, and ensure unique key material for each session per RFC 7296 requirements.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Zxun EpdgApplication
Affected:< 5.20.20

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ZTE ZXUN-ePDG presence
    Inventory network devices or check for 'ZXUN-ePDG' or 'Zxun Epdg' in device naming, documentation, or management interfaces
    Affected if The device is not present in your environment - you are not affected
  2. Identify installed version
    Access the ZXUN-ePDG management interface or CLI and retrieve the software version (typically via 'show version' or system information page)
    Affected if Version is below 5.20.20 - your version is within the affected range
  3. Verify IKE key configuration
    Access the IPsec/IKE configuration section in the ZXUN-ePDG management interface or config files and examine whether pre-shared keys (PSKs) or static keys are configured for IKE security associations
    Affected if Default, static, or pre-configured PSKs are in use rather than dynamically generated per-session keys - the vulnerability condition is present
  4. Confirm key uniqueness
    Review IKE logs or key management configuration to determine if unique key material is generated per session per RFC 7296 requirements
    Affected if Keys are reused across sessions or are hardcoded/default values - the flaw is exploitable in your environment

You are affected if you have ZXUN-ePDG version below 5.20.20 AND are using default/static cryptographic keys for IKE instead of unique per-session keys.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.20.20 or later
Fixed in 5.20.20
Interim mitigation

Replace default/static cryptographic keys with unique, properly generated per-session keys following IKE best practices. Implement proper key management, rotation, and ensure unique key material for each session per RFC 7296 requirements.

Recommended fix Moderate confidence

ZTE ZXUN-ePDG version 5.20.20 or later

  1. 1. Identify the current version of ZTE ZXUN-ePDG by checking the system administration interface or running the appropriate version command
  2. 2. Verify the current IKE configuration to confirm it is using the default/non-unique cryptographic keys as described in the vulnerability
  3. 3. Plan maintenance window for the upgrade (IKE connections will be briefly interrupted during upgrade)
  4. 4. Back up the current configuration of the ZXUN-ePDG system before proceeding
  5. 5. Upgrade the ZXUN-ePDG software to version 5.20.20 or later following standard ZTE upgrade procedures
  6. 6. After upgrade, verify the new version is correctly installed
  7. 7. Reconfigure IKE to use unique, strong cryptographic keys instead of default values if the upgrade alone does not change them
  8. 8. Test IKE connections with mobile devices to confirm secure connectivity is working
Caveat Standard upgrade risks apply - ensure backup before proceeding; brief service interruption during upgrade process

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zxun Epdg Scoped from the published advisory
  • Consultation12.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,784.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22064 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-22064 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data