Information disclosure in Apache MXNet
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA. Impact type from CWE-200.
Summary
The clustered setup of Apache MXNet allows users to specify which IP address and port the scheduler will listen on via the DMLC_PS_ROOT_URI and DMLC_PS_ROOT_PORT env variables. In versions older than 1.0.0, however, the MXNet framework will listen on 0.0.0.0 rather than user specified DMLC_PS_ROOT_URI once a scheduler node is initialized. This exposes the instance running MXNet to any attackers reachable via the interface they didn't expect to be listening on. For example: If a user wants to run a clustered setup locally, they may specify to run on 127.0.0.1. But since MXNet will listen on 0.0.0.0, it makes the port accessible on all network interfaces.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
- Fix · CNA Apache MXNet (Apache Software Foundation) Fixed in 1.0.0
Timeline
- 2026-10-02 Threatist record created from CVE-2018-1281
- 2026-10-03 Alias added: GHSA-96h5-25jj-74vc
More Apache Mxnet vulnerabilities
- TI-2022-08175 ReDoS in Apache MXNet RTC Module CVSS 3.1HIGH 7.5
Sources
- CVE-2018-1281 · CVE Program
- CVE-2018-1281 · NVD
- FIRST EPSS
- GHSA-96h5-25jj-74vc · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences