Cross-device property modification via inconsistent device identity
Published Sep 30, 2024 · Updated Sep 30, 2024
Improper privilege management in TP-Link Kasa KP125M 1.0.3 allows remote authenticated users to alter other devices' cloud properties. The /common/v1/uploadDeviceInfo API checks the deviceId and deviceToken parameters but accepts a different deviceId in the request body. Remote authenticated users need a legitimate device connection to the MQTT broker; forged properties can block the owner's mobile-app access without damaging the plug.
Summary
What happened
Improper privilege management in TP-Link Kasa KP125M 1.0.3 allows remote authenticated users to alter other devices' cloud properties. The /common/v1/uploadDeviceInfo API checks the deviceId and deviceToken parameters but accepts a different deviceId in the request body. Remote authenticated users need a legitimate device connection to the MQTT broker; forged properties can block the owner's mobile-app access without damaging the plug.
The record
- CVE
- CVE-2024-46549
- Published
- Sep 30, 2024
- Updated
- Sep 30, 2024
- Vendor
- TP-Link
- Product
- Kasa Smart Wi-Fi Plug Slim, Energy Monitoring (KP125M)
- Classifications
- CWE-269
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 30, 2024CVE publishedPublication date reported by the CVE source.
- Sep 30, 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=1.0.3
What conditions does exploitation require?
What is affected?
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
- uploadDeviceInfo deviceId substitution reproductionproof 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