Quick answers
- Is CVE-2024-29225 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-29225 being exploited in the wild.
- How severe is CVE-2024-29225?
- Medium severity, with a CVSS score of 4.3, published 4 April 2024.
- Which products and versions are affected?
- Elecom WMC-2LX-B v1.42 and earlier; Elecom WMC-X1800GST-B v1.42 and earlier; Elecom WRC-G01-W v1.24 and earlier; Elecom WRC-X3200GST3-B v1.25 and earlier; and 1 more.
- Is there a fix for CVE-2024-29225?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2024-29225 attacked?
- It is attacked from the adjacent network, in a network appliance.
- Am I affected by CVE-2024-29225?
- Check whether you run Elecom WMC-2LX-B, Elecom WMC-X1800GST-B, Elecom WRC-G01-W or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is classified as an exposure of sensitive information (CWE-552/CWE-200) within the web management interface of several ELECOM router models. An unauthenticated attacker located on the same local network (adjacent) can bypass intended access controls by sending a specially crafted HTTP request to the device. This request triggers the unauthorized download of the router's configuration file. Successful exploitation allows the attacker to read sensitive configuration parameters, which may include administrative credentials or network secrets. Firmware updates have been released to address this issue.
Affected products
- ELECOM WRC-X3200GST3-B v1.25 and earlier
- ELECOM WRC-G01-W v1.24 and earlier
- ELECOM WMC-2LX-B v1.42 and earlier
- ELECOM WMC-X1800GST-B v1.42 and earlier
- ELECOM WSC-X1800GS-B v1.42 and earlier
Timeline
- 2024-03-26: advisory: Initial advisory published by JVN/JPCERT
- 2024-04-04: disclosed: CVE published to NVD