# CVE-2018-1041: Denial of service in jboss-remoting

> An attacker can cause a denial of service via high CPU usage due to an infinite loop in the RemoteMessageChannel component of the JBoss Remoting library.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r69p-rc7c-rr2m

## What is CVE-2018-1041?

CVE-2018-1041 is a high-severity denial of service vulnerability in Redhat Jboss Enterprise Application Platform, published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in the way RemoteMessageChannel, introduced in jboss-remoting versions 3.3.10, reads from an empty buffer. An attacker could use this flaw to cause denial of service via high CPU caused by an infinite loop.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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

It affects 2 products.


Products: Jboss Jboss-Remoting, Redhat Jboss Enterprise Application Platform.

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

Upgrade to a fixed version.

## Is CVE-2018-1041 being exploited?

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

Public exploit code:

- JBoss Remoting 6.14.18 - Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1041 is a high-severity denial of service vulnerability in Redhat Jboss Enterprise Application Platform, published on 15 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1041 in the wild and no public exploit code.

Affected product: Redhat Jboss Enterprise Application Platform. 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-1041/ (Markdown: https://insights.sbomify.com/CVE-2018-1041/index.md)
```

## Sources

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

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