Provisioning data disclosure via shared encryption key
Published Feb 23, 2024 · Updated Nov 4, 2025
Hardcoded keys in Yealink Configuration Encrypt Tool AES and RSA editions before 1.2 allow remote attackers to read provisioning data. The tool encrypts provisioning documents with a static AES key shared across customers, exposing plaintext credentials and enabling forged files that phones trust. Exploitation requires access to files distributed by HTTP, FTP, or TFTP; exposed data can include usernames, passwords, server hosts, and caller IDs.
Summary
What happened
Hardcoded keys in Yealink Configuration Encrypt Tool AES and RSA editions before 1.2 allow remote attackers to read provisioning data. The tool encrypts provisioning documents with a static AES key shared across customers, exposing plaintext credentials and enabling forged files that phones trust. Exploitation requires access to files distributed by HTTP, FTP, or TFTP; exposed data can include usernames, passwords, server hosts, and caller IDs.
The record
- CVE
- CVE-2024-24681
- Published
- Feb 23, 2024
- Updated
- Nov 4, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, CAPEC-191, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 23, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo