Eap Controller
Approved changes feed: RSS · Atom
cpe:2.3:a:tp-link:eap_controller:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Tp Link (0b2e1553-ac8b-5981-a60b-ca6c27ee3a6e) |
|---|---|
| Product | Eap Controller (e95af700-080c-523c-91a9-194135cf03d8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-5393 |
vulnerable | 2026-06-08 05:11:50.849463 |
TP-Link EAP Controller versions 2.5.3 and earlier lack RMI authentication
The TP-LINK EAP Controller is TP-LINK's software for remotely controlling wireless access point devices. It utilizes a Java remote method invocation (RMI) service for remote control. The RMI interface does not require any authentication before use, so it lacks user authentication for RMI service commands in EAP controller versions 2.5.3 and earlier. Remote attackers can implement deserialization attacks through the RMI protocol. Successful attacks may allow a remote attacker to remotely control the target server and execute Java functions or bytecode.
Published: 2018-09-28T17:00:00.000Z
Updated: 2024-08-05T05:33:44.241Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.