Skip to content
Fencer Vulns
high 7.5

CVE-2018-11793 json

Stack Overflow in Apache Mesos

published 2019-03-05 7 y ago modified 2026-06-17 4 mo ago also GHSA-p2xq-vcm7-xjj6 , EUVD-2019-0387

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

Summary

When parsing a JSON payload with deeply nested JSON structures, the parser in Apache Mesos versions pre-1.4.x, 1.4.0 to 1.4.2, 1.5.0 to 1.5.1, 1.6.0 to 1.6.1, and 1.7.0 might overflow the stack due to unbounded recursion. A malicious actor can therefore cause a denial of service of Mesos masters rendering the Mesos-controlled cluster inoperable.

Patch / fix

  • maven org.apache.mesos:mesos 1.4.3, 1.5.2, 1.6.2, 1.7.1
  • apache mesos 1.4.3, 1.5.2, 1.6.2, 1.7.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-11793 updated cvss 5.6

mesos: stack overflow vulnerability in parser

  • Red Hat Fuse 7 mesos mesos
    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

4.97% chance of exploitation in the next 30 days, higher than 92% 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.3
>=1.5.0, <1.5.2
>=1.6.0, <1.6.2
>=1.7.0, <1.7.1
1.4.3
1.5.2
1.6.2
1.7.1

Affected products

  • Apache Software Foundation Apache Mesos

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

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.