dbcve.org
MesosApplication · Apache

CVE-2018-1330

HIGH · 7.5 CVSS v3.0 Published 2018-09-13
Fix available
A fix is available. Upgrade to 1.4.2 / 1.5.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Mesos libprocess in versions 1.4.0 to 1.5.0 crashes when parsing malformed JSON payloads due to an uncaught exception, and also crashes when handling chunked HTTP requests with trailers due to a mistakenly planted assertion. An attacker can send specially crafted requests to cause a denial of service on Mesos masters.

MitigationUpgrade Apache Mesos to version 1.5.1 or later to receive the fix for the uncaught exception and the mistaken assertion.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MesosApplication
Affected:>= 1.4.0, < 1.4.2>= 1.5.0, < 1.5.1= 1.4.0= 1.6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Mesos master version
    Run `mesos-master --version` or check the package version with `dpkg -l | grep mesos` (Debian) or `rpm -qa | grep mesos` (RHEL/CentOS)
    Affected if The version is 1.4.0, 1.4.1, 1.5.0, or 1.6.0 (any version >= 1.4.0 and < 1.4.2, or >= 1.5.0 and < 1.5.1, or exactly 1.6.0)
  2. Locate Mesos binary path
    Run `which mesos-master` or `find /usr -name mesos-master 2>/dev/null` to confirm the installation location
    Affected if The binary exists and the version check above shows an affected version
  3. Verify Mesos master service is running
    Run `systemctl status mesos-master` or `ps aux | grep mesos-master` to confirm the master process is active
    Affected if The master is running and the version is in the affected range listed above

You are affected if a Mesos master is running version 1.4.0, 1.4.1, 1.5.0, or 1.6.0, as these versions contain the uncaught exception and mistaken assertion that cause crashes on malformed JSON or chunked HTTP requests with trailers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.4.2 / 1.5.1 or later
Fixed in 1.4.21.5.1
Interim mitigation

Upgrade Apache Mesos to version 1.5.1 or later to receive the fix for the uncaught exception and the mistaken assertion.

Fix this in Mesos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1330 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1330 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data