CVE-2024-24681: Critical severity Yealink Configuration Encryption Tool vulnerability

Published Feb 23, 2024
·
Updated

An issue was discovered in Yealink Configuration Encrypt Tool (AES version) and Yealink Configuration Encrypt Tool (RSA version before 1.2). There is a single hardcoded key (used to encrypt provisioning documents) across customers' installations.

Affected Software

4 affected components
Yealink Configuration Encryption Tool<1.2
Yealink Configuration Encryption Tool
Yealink Configuration Encrypt Tool (AES version)
Yealink Configuration Encrypt Tool (RSA version)<1.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Yealink Configuration Encrypt Tool (RSA version) to a version that resolves this vulnerability.

    Fixed in 1.2
  2. Operational

    Replace/rotate the hardcoded encryption key used by Yealink Configuration Encrypt Tool (AES version) and Yealink Configuration Encrypt Tool (RSA version before 1.2), since the same single key is shared across customers' installations.

Event History

Feb 23, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·11:15 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-24681?

CVE-2024-24681 is considered a high severity vulnerability due to the presence of a hardcoded encryption key across multiple customer installations.

2

How do I fix CVE-2024-24681?

To fix CVE-2024-24681, update to the latest version of the Yealink Configuration Encrypt Tool that addresses the hardcoded key issue.

3

Which versions of Yealink Configuration Encrypt Tool are affected by CVE-2024-24681?

CVE-2024-24681 affects all versions of the Yealink Configuration Encrypt Tool (RSA version prior to 1.2 and all versions of AES version).

4

What is the impact of CVE-2024-24681 on customer data?

CVE-2024-24681 may lead to unauthorized access to encrypted provisioning documents due to the use of a shared hardcoded key.

5

Is there a workaround for CVE-2024-24681 while awaiting a patch?

Currently, there is no recommended workaround for CVE-2024-24681; users should prioritize upgrading to a secure version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203