Apache MXNet における情報漏えいに関する脆弱性
| Title |
Apache MXNet における情報漏えいに関する脆弱性
|
| Summary |
Apache MXNet には、情報漏えいに関する脆弱性が存在します。
|
| Possible impacts |
情報を取得される可能性があります。 |
| Solution |
ベンダ情報および参考情報を参照して適切な対策を実施してください。 |
| Publication Date |
June 8, 2018, midnight |
| Registration Date |
Aug. 20, 2018, 3:24 p.m. |
| Last Update |
Aug. 20, 2018, 3:24 p.m. |
|
CVSS3.0 : 警告
|
| Score |
6.5
|
| Vector |
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
|
CVSS2.0 : 警告
|
| Score |
4
|
| Vector |
AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected System
| Apache Software Foundation |
|
Apache MXNet 1.0.0 未満
|
CVE (情報セキュリティ 共通脆弱性識別子)
CWE (共通脆弱性タイプ一覧)
ベンダー情報
その他
Change Log
| No |
Changed Details |
Date of change |
| 1 |
[2018年08月20日]
掲載 |
Aug. 20, 2018, 3:24 p.m. |
NVD Vulnerability Information
CVE-2018-1281
| 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.
|
| Publication Date |
June 9, 2018, 4:29 a.m. |
| Registration Date |
March 1, 2021, 6:51 p.m. |
| Last Update |
Nov. 21, 2024, 12:59 p.m. |
Affected software configurations
| Configuration1 |
or higher |
or less |
more than |
less than |
| cpe:2.3:a:apache:mxnet:*:*:*:*:*:*:*:* |
|
|
|
1.0.0 |
Related information, measures and tools
Common Vulnerabilities List