Physical account takeover via flawed factory reset
Published Apr 25, 2024 · Updated Sep 6, 2024
Improper authentication in Yealink VP59 Teams firmware 91.15.0.118 allows physically proximate attackers to take over an account. The disclosed proof of concept uses crafted physical key presses against the factory-reset procedure after a Teams account is configured and the phone locks. Physical access to the device is required, and Yealink has not published which authentication check the reset path omits.
Summary
What happened
Improper authentication in Yealink VP59 Teams firmware 91.15.0.118 allows physically proximate attackers to take over an account. The disclosed proof of concept uses crafted physical key presses against the factory-reset procedure after a Teams account is configured and the phone locks. Physical access to the device is required, and Yealink has not published which authentication check the reset path omits.
The record
- CVE
- CVE-2024-30939
- Published
- Apr 25, 2024
- Updated
- Sep 6, 2024
- Vendor
- Yealink
- Product
- Yealink VP59 Firmware
- Classifications
- CWE-287, T1078
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 25, 2024CVE publishedPublication date reported by the CVE source.
- Sep 6, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=91.15.0.118
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- Yealink IP Phone Account Take Over proof of conceptproof of concept · demonstrated
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