dbcve.org
Configuration Encryption ToolApplication · Yealink

CVE-2024-24681

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-23
Fix available
A fix is available. Upgrade to 1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
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.

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 · high confidence

Yealink Configuration Encrypt Tool (both AES and RSA versions before 1.2) contains a single hardcoded cryptographic key used to encrypt provisioning documents. This key is identical across all customer installations, allowing anyone who discovers the key to decrypt any customer's provisioning configurations.

MitigationReplace the hardcoded key with a unique, customer-specific key or device-specific key. Re-encrypt all provisioning documents using the updated tool (version 1.2 or later) and redeploy to devices.

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
Configuration Encryption ToolApplication
Affected:< 1.2all versions

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify if Yealink Configuration Encrypt Tool is in use
    Search for the tool executable (e.g., ConfigEncryptTool.exe, yealink_config_encrypt, or similar) on systems where provisioning configurations are managed or generated. Check installation directories used for Yealink management tools.
    Affected if The tool is found on any system used for provisioning configuration management.
  2. Check tool version
    Right-click the executable, select Properties, and view the File Version or Product Version field. Alternatively, run the tool with a version flag if available (e.g., --version or -v).
    Affected if The reported version is below 1.2 (e.g., 1.0, 1.1, or any version number less than 1.2).
  3. Locate provisioning configuration files
    Search for Yealink provisioning files in use: .cfg, .xml, .bin, or encrypted equivalents (often in /config or /provisioning directories on the provisioning server). Look for files matching patterns like *autop*.cfg, *y000*, or MAC-address-named files.
    Affected if Encrypted provisioning configuration files exist that were generated using the affected tool versions.
  4. Inspect encryption configuration
    Open the tool or its configuration files to verify whether a custom, customer-specific key was provided during encryption, versus using the default key shipped with the tool. Check for any key configuration files or logs showing key derivation parameters.
    Affected if The encryption was performed using the default key without any customer-specific or device-specific customization.

You are affected if you are using Yealink Configuration Encryption Tool version 1.1 or earlier to encrypt provisioning configurations, or if you have provisioning files that may have been encrypted using the default hardcoded key.

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 1.2 or later
Fixed in 1.2
Interim mitigation

Replace the hardcoded key with a unique, customer-specific key or device-specific key. Re-encrypt all provisioning documents using the updated tool (version 1.2 or later) and redeploy to devices.

Recommended fix High confidence

1.2

  1. Obtain version 1.2 of Yealink Configuration Encrypt Tool from the official Yealink website or authorized distribution channels
  2. Backup all existing encrypted provisioning configuration files before making changes
  3. Uninstall or replace the vulnerable version (< 1.2) of the Configuration Encrypt Tool
  4. Install the fixed version 1.2 of the Configuration Encrypt Tool
  5. Re-encrypt all provisioning documents using the updated tool to ensure they use the new key rather than the compromised hardcoded key
  6. Verify that the encryption is working correctly with the new version
  7. Securely dispose of any copies of the old tool and ensure the hardcoded key is no longer in use

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

Fix this in Configuration Encryption Tool Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24681 — 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-24681 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