Denial of service in Apache Mesos
Published 13 May 2022 · Updated 28 Nov 2024
Is your project on an affected org.apache.mesos:mesos?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <1.1.3
- Fixed in
- 1.1.3
mvn versions:use-dep-version -Dincludes=org.apache.mesos:mesos -DdepVersion=1.1.3 -DforceVersion=true- Affected
- >=1.2.0 <1.2.2
- Fixed in
- 1.2.2
mvn versions:use-dep-version -Dincludes=org.apache.mesos:mesos -DdepVersion=1.2.2 -DforceVersion=true- Affected
- >=1.3.0 <1.3.1
- Fixed in
- 1.3.1
mvn versions:use-dep-version -Dincludes=org.apache.mesos:mesos -DdepVersion=1.3.1 -DforceVersion=trueDetails
When handling a decoding failure for a malformed URL path of an HTTP request, libprocess in Apache Mesos might crash because the code accidentally calls inappropriate function. A malicious actor can therefore cause a denial of service of Mesos masters rendering the Mesos-controlled cluster inoperable.
Is GHSA-x869-784m-jmj2 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.mesos:mesos, and gives you the command that fixes it.
More advisories for org.apache.mesos:mesos
- HighCVE-2018-1330Crash when decoding malformed HTTP requests or malformed JSON payload · 14 May 2022
- HighCVE-2017-9790Use after free in Apache Mesos · 13 May 2022
- HighCVE-2019-0204Docker image code execution with Apache Mesos · 13 May 2022
- HighCVE-2018-11793Stack Overflow in Apache Mesos · 6 Mar 2019
- MediumCVE-2018-8023Moderate severity vulnerability that affects org.apache.mesos:mesos · 17 Oct 2018
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.