Update Time:June 12nd,2025
Yealink received a vulnerability report submitted to Yealink Security by an external security researcher in May 2025. Yealink is actively processing and evaluating it according to the Yealink Vulnerability Disclose Process(VDP) as we understand your concerns about possible vulnerabilities. As a close partner of Yealink, we have the responsibility and obligation to proactively communicate with you as soon as possible. Please see the following description of the progress of vulnerability handling for details.
ISSUE:
1) RPS & Device CA Issue
Issue description: The device certificates issued by Yealink Equipment Issuing CA before 2020 have a forgery vulnerability, which may cause the risk of device identity forgery. This certificate is used for device and RPS-related services .
ANALYSES:
Yealink statement: This Issue only exists in devices sold before 2020, and new devices do not have this Issue. At the same time, because the certificate is used to interact with the RPS server, the current RPS server has added multiple verification measures to prevent malicious traversal attacks. Abnormal behaviors will be locked and added to the blacklist to ensure the security of your information.
SOLUTION:
Mitigation measures:
For Yealink IP Phone products purchased before 2020, we recommend that you upgrade the firmware to strengthen the security access control of the device and RPS for higher security protection.
Recommended upgrade version | ||
SIP-T19P_E2 | lower than 53.84.0.121 | 53.84.0.160 or higher |
SIP-T21P_E2 | lower than 52.84.0.121 | 52.84.0.160 or higher |
SIP-T23G | lower than 44.84.0.121 | 44.84.0.160 or higher |
SIP-T40G | lower than 76.84.0.121 | 76.84.0.160 or higher |
SIP-T40P | lower than 54.84.0.121 | 54.84.0.160 or higher |
SIP-T27G | lower than 69.84.0.121 | 69.86.0.160 or higher |
SIP-T41S, T42S, T46S, T48S | lower than 66.84.0.121 | 66.86.0.83 or higher |
SIP-CP920 | lower than 78.84.0.121 | 78.86.0.15 or higher |
SIP-T53, T53W, T54W, T57W | lower than X.84.0.121 | 96.86.0.75 or higher |
SIP-T56A, T58 | lower than 58.84.0.37 | 58.86.0.160 or higher |
W52P | lower than 25.81.0.67 | 25.81.0.160 or higher |
W60B | lower than 77.83.0.83 | 77.85.0.160 or higher |
CP960 | lower than 73.84.0.37 | 73.86.0.160 or higher |
SIP- T27P | 45.83.0.160 and below | 45.83.0.161 or higher |
SIP-T29G | 46.83.0.160 and below | 46.83.0.161 or higher |
SIP-T41P | 36.83.0.160 and below | 36.83.0.161 or higher |
SIP-T42G | 29.83.0.160 and below | 29.83.0.161 or higher |
SIP-T46G | 28.83.0.160 and below | 28.83.0.161 or higher |
SIP-T48G | 35.83.0.160 and below | 35.83.0.161 or higher |
SIP-T20P | No longer providing RPS service | No longer providing RPS service |
SIP-T22P | No longer providing RPS service | No longer providing RPS service |
SIP-T26P | No longer providing RPS service | No longer providing RPS service |
SIP-T27P | No longer providing RPS service | No longer providing RPS service |
T52S/T54S | No longer providing RPS service | No longer providing RPS service |
2) RPS Certificate Content Validation Bypass Vulnerability
Issue description: Using the RPS web interface it is possible to upload any file smaller than 5Mb for as long as the file extention is ".pem".
SOLUTION:
Yealink statement: The device itself has a secondary verification of the certificate format, which will not actually cause any impact. The RPS platform has been optimized and fixed this issue.
Mitigation measures:
For detailed fix disclosure, please see: https://www.yealink.com/en/trust-center/security-advisories/ecb16a4993014d22
3) RPS Device SN Last-Five-Digit Enumeration Vulnerability
Issue description: It has been possible to enumerate the last 5 digits of the serial number of a device.
SOLUTION:
Yealink Statement: This issue has been optimized and fixed.
Mitigation measures:
For detailed fix disclosure, please see: https://www.yealink.com/en/trust-center/security-advisories/b8dc062eaa8d4f59
4) RPS API Rate Limiting Missing Vulnerability
Issue description: RPS API lacks rate limiting controls, potentially enabling excessive request exploitation.
SOLUTION:
Yealink Statement: This issue has been optimized and fixed.
Mitigation measures:
https://www.yealink.com/en/trust-center/security-advisories/f8205560a8c7443f
5) Frozen Enterprise OpenAPI Access Control Bypass Vulnerability
Issue description: YMCS&RPS fails to enforce access restrictions on OpenAPI for frozen enterprise accounts, allowing unauthorized access to deactivated interfaces.
SOLUTION:
Yealink Statement: This issue has been optimized and fixed.
Mitigation measures:
https://www.yealink.com/en/trust-center/security-advisories/1318c5efb82e4526
Finally, we promise that safety is Yealink’s persistent goal. We will work with you to continuously improve product safety and address any of your concerns as soon as possible.
We therefore will follow the vulnerability disclosure process to conduct a series of measures after a vulnerability is reported. Currently, we recommend that you follow the above guidelines to ensure safety in this issue.
Reported vulnerability will be disclosed on our website, see: https://www.yealink.com/en/trust-center/security-advisories