Crash when decoding malformed HTTP requests or malformed JSON payload

published 2018-09-13 8 y ago modified 2026-06-17 4 mo ago also GHSA-95q3-pppp-r683 , EUVD-2022-3293

cvss: 7.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 3.7%; EPSS 3.7% chance of exploitation in 30 days, percentile 89%
public exploits: 0; none known

When parsing a malformed JSON payload, libprocess in Apache Mesos versions 1.4.0 to 1.5.0 might crash due to an uncaught exception. Parsing chunked HTTP requests with trailers can lead to a libprocess crash too because of the mistakenly planted assertion. A malicious actor can therefore cause a denial of service of Mesos masters rendering the Mesos-controlled cluster inoperable.

Patch / fix

fixed in 2

maven org.apache.mesos:mesos 1.6.0
apache mesos 1.4.2, 1.5.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1330 updated 2026-01-13 cvss 7.5

mesos: Libprocess crashes when decoding malformed HTTP requests or malformed JSON payload

Red Hat All currently supported Red Hat products
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.74% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.0	7.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub	3.0	7.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	org.apache.mesos:mesos	>=1.4.0, <1.6.0	1.6.0

Affected products

Apache Software Foundation Apache Mesos

Classification

Weakness

CWE-20 Improper Input Validation
CWE-248 Uncaught Exception

References

Sources

CVE List CVE-2018-1330
GitHub Advisory GHSA-95q3-pppp-r683
NVD CVE-2018-1330

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary