Description
Inadequate encryption strength vulnerability in multiple routers provided by ELECOM CO.,LTD. and LOGITEC CORPORATION allows a network-adjacent unauthenticated attacker to guess the encryption key used for wireless LAN communication and intercept the communication. As for the affected products/versions, see the information provided by the vendor under [References] section.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| ELECOM | WRC-2533GHBK2-T | all versions | — |
| ELECOM | WRC-2533GHBK-I | all versions | — |
| ELECOM | WRC-1750GHBK2-I | all versions | — |
| ELECOM | WRC-1750GHBK-E | all versions | — |
| ELECOM | WRC-1750GHBK | all versions | — |
| ELECOM | WRC-1167GHBK2 | all versions | — |
| ELECOM | WRC-1167GHBK | all versions | — |
| ELECOM | WRC-F1167ACF | all versions | — |
| ELECOM | WRC-733GHBK | all versions | — |
| ELECOM | WRC-733GHBK-I | all versions | — |
| ELECOM | WRC-733GHBK-C | all versions | — |
| ELECOM | WRC-300GHBK2-I | all versions | — |
| ELECOM | WRC-300GHBK | all versions | — |
| ELECOM | WRC-733FEBK | all versions | — |
| ELECOM | WRC-300FEBK | all versions | — |
| ELECOM | WRC-F300NF | all versions | — |
| ELECOM | WRH-300WH-H | all versions | — |
| ELECOM | WRH-300BK | all versions | — |
| ELECOM | WRH-300WH | all versions | — |
| ELECOM | WRH-300RD | all versions | — |
| ELECOM | WRH-300SV | all versions | — |
| ELECOM | WRH-300BK-S | all versions | — |
| ELECOM | WRH-300WH-S | all versions | — |
| ELECOM | WRH-300BK2-S | all versions | — |
| ELECOM | WRH-300WH2-S | all versions | — |
| ELECOM | WRH-H300BK | all versions | — |
| ELECOM | WRH-H300WH | all versions | — |
| ELECOM | WRH-150BK | all versions | — |
| ELECOM | WRH-150WH | all versions | — |
| ELECOM | LAN-W300N/RS | all versions | — |
| ELECOM | LAN-W301NR | all versions | — |
| ELECOM | LAN-W300N/P | all versions | — |
| ELECOM | LAN-WH300N/DGP | all versions | — |
| ELECOM | LAN-WH300NDGPE | all versions | — |
Public exploits
Exploit or proof-of-concept code for this vulnerability is publicly available, which lowers the bar for attackers. Treat it as a reason to patch sooner.
Third-party code, not reviewed by us. Public PoCs are sometimes fake or contain malware. Read the code first and run it only in an isolated lab, against systems you are authorised to test.
GitHub 1 repository
-
sharmashreejaa/CVE-2023-43757 ★ 0 · Feb 28, 2024
Sources: PoC-in-GitHub, Metasploit Framework, Exploit-DB — updated daily. Only links are listed; no exploit code is hosted here.