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.
References
Link | Resource |
---|---|
https://github.com/dmlc/ps-lite/commit/4be817e8b03e7e92517e91f2dfcc50865e91c6ea | Patch Third Party Advisory |
https://github.com/dmlc/ps-lite/commit/4be817e8b03e7e92517e91f2dfcc50865e91c6ea | Patch Third Party Advisory |
Configurations
History
21 Nov 2024, 03:59
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/dmlc/ps-lite/commit/4be817e8b03e7e92517e91f2dfcc50865e91c6ea - Patch, Third Party Advisory |
Information
Published : 2018-06-08 19:29
Updated : 2024-11-21 03:59
NVD link : CVE-2018-1281
Mitre link : CVE-2018-1281
CVE.ORG link : CVE-2018-1281
JSON object : View
Products Affected
apache
- mxnet
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor