Loading vulnerability…
The Aqara Cloud Developer Portal at developer.aqara.com improperly allowed creation of a developer account and issuance of developer credentials for attacker-controlled registrations without a meaningful authentication or approval control. According to the provided content, the endpoint POST /open-server/authcode/get accepted any email address supplied by the attacker, sent a verification code to that address, and allowed completion of developer signup without an approval workflow. As a result, an otherwise unauthenticated remote attacker could obtain a valid developer Appid/Keyid pair and corresponding developer token. The issue is described as missing authentication for a critical function because the portal treated possession of any reachable email inbox as sufficient to access a sensitive developer-enrollment function that should have been restricted or vetted. The vulnerability is significant because the issued developer credentials were reportedly usable against Aqara production APIs and could serve as the first step in a broader attack chain.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.