Skip to content
Fencer Intel
high 8.8

CVE-2019-15745 json

The Eques elf smart plug and the mobile app use a hardcoded AES 256 bit key to encrypt the commands and responses between the device and th…

published 7y ago modified 4mo ago also EUVD-2019-6680

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

The Eques elf smart plug and the mobile app use a hardcoded AES 256 bit key to encrypt the commands and responses between the device and the app. The communication happens over UDP port 27431. An attacker on the local network can use the same key to encrypt and send commands to discover all smart plugs in a network, take over control of a device, and perform actions such as turning it on and off.

Is CVE-2019-15745 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.38% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • ckn.io https://www.ckn.io/blog/2019/08/27/exploiting-the-eques-elf-smart-plug-part-one/ referenced PoC, tagged "exploit" by a source, unverified
  • ckn.io https://www.ckn.io/blog/2019/08/27/exploiting-the-eques-elf-smart-plug-part-two/ referenced PoC, tagged "exploit" by a source, unverified
  • ckn.io https://www.ckn.io/blog/2019/08/27/exploiting-the-eques-elf-smart-plug-part-three/ referenced PoC, tagged "exploit" by a source, unverified
  • ckn.io https://www.ckn.io/blog/2019/08/27/exploiting-the-eques-elf-smart-plug-part-four/ referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/iamckn/eques referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 3.3 AV:A/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-798 Use of Hard-coded Credentials

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.