CVE-2025-15631

CVE-2025-15631 concerns weak credential hashing in TP-Link's Omada controller, a controller-based networking platform where 'site credentials' gate access not to a single device but to a management plane overseeing potentially hundreds of access points, switches, and gateways. The CVE labels this a 'legacy hashing algorithm' — but 'legacy' in vendor disclosures often obscures a deliberate historical choice that seemed reasonable at the time but has aged poorly. The real failure isn't a single algorithm decision; it's the absence of cryptographic agility — the architectural inability to swap out primitives without breaking the installed base. The attack surface here extends well beyond the device itself. If site credentials are stored in config exports that administrators back up, restore across devices, or share with support, the attack surface becomes any config archive — whether obtained through supply chain compromise, physical access to a backup, or a support ticket mishandling. One cracked hash doesn't unlock one box; it unlocks the management plane for the entire deployment. That blast radius is what makes this significant despite the modest CVSS 5.9. Three questions drive the real risk assessment. First, what algorithm is actually in use? The distinction between 'merely legacy' (PBKDF2 with low iterations) and 'known-to-be-weak' (MD5, SHA1) changes whether practical offline cracking at scale is feasible. Second, can credential rotation happen independently of firmware updates, or does remediation require a full firmware cycle across heterogeneous deployments? If the latter, the coordination friction compounds the technical vulnerability. Third, does the vendor's current product line still ship with this credential architecture, or is this isolated to older firmware? Active products with the same flaw represent a fundamentally different risk than a dormant bug in end-of-lifed hardware. The low EPSS (0.64%) and moderate CVSS create a false comfort. These metrics describe current attacker economics, not the underlying exposure architecture. Embedded devices with weak crypto that lack update pathways represent a persistent surface that waits for new attack classes or access vectors. The question isn't whether this specific hash is being exploited today — it's whether your deployment model (config backups, support workflows, physical access exposure) makes the path from config archive to management plane compromise economically viable for an attacker who already has Foothold. Assume the hash is crackable until proven otherwise, treat any config archive as credential-equivalent, and pressure the vendor for a timeline on both algorithm remediation and architectural hardening.

Reviewed through automated stages and approved by a human before publication.