# CVE-2018-1281: Misconfiguration in Apache MXNet

> Apache MXNet scheduler binds to all interfaces instead of the configured IP, exposing the service to unintended networks.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-96h5-25jj-74vc

## What is CVE-2018-1281?

CVE-2018-1281 is a medium-severity vulnerability in Apache MXNet, published on 8 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-1281?

It affects 1 product.


Products: Apache Mxnet.

## How do I fix CVE-2018-1281?

No fix has been published for CVE-2018-1281 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-1281 being exploited?

There is no known exploitation of CVE-2018-1281 in the wild and no public exploit code.

## Other vulnerabilities in Apache MXNet

- [CVE-2022-24294](https://insights.sbomify.com/CVE-2022-24294/): ReDoS in Apache MXNet RTC Module (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1281 and fix it if it is affected.

What it is: CVE-2018-1281 is a medium-severity vulnerability in Apache MXNet, published on 8 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1281 in the wild and no public exploit code.

Affected product: Apache MXNet. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-1281/ (Markdown: https://insights.sbomify.com/CVE-2018-1281/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-1281
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-1281
- OSV: https://osv.dev/vulnerability/CVE-2018-1281

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-1281/
Summaries are generated and may contain mistakes; the official description above is the record.