`CVE-2017-9790`

7.5 High No exploit published

Description

When handling a libprocess message wrapped in an HTTP request, libprocess in Apache Mesos before 1.1.3, 1.2.x before 1.2.2, 1.3.x before 1.3.1, and 1.4.0-dev crashes if the request path is empty, because the parser assumes the request path always starts with '/'. A malicious actor can therefore cause a denial of service of Mesos masters rendering the Mesos-controlled cluster inoperable.

CWE-416 · Use after free

Exploitation Status

No public exploit

Nothing published shows this CVE being exploited, which is not the same as ruling it out. nothing published in 8 years.

CVSS E:U

CISA KEV not listed
CISA Vulnrichment no assessment published
Indexed PoC none indexed
EPSS 2.4% chance in 30 days

Waratek Defense Posture

No exploit published

In RASP's scope with an upstream fix path, but nobody has published a working exploit. That is a statement about what has been published, not a finding that the defect is unreachable or unimportant.

Protection none
Action unverified patch rule
Review automated upstream-data
Record active

Decided by no-exploit-published : A published working exploit for this candidate, not only a proof of concept, a forecast, or nothing at all

Finding This CVE is not listed in CISA KEV, CISA Vulnrichment records no active exploitation, and no reviewed exploit catalogue carries an entry for it. Nobody has published something a stranger can run, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.

Decided by	`no-exploit-published` : A published working exploit for this candidate, not only a proof of concept, a forecast, or nothing at all
Finding	This CVE is not listed in CISA KEV, CISA Vulnrichment records no active exploitation, and no reviewed exploit catalogue carries an entry for it. Nobody has published something a stranger can run, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.

CVSS

7.5 HIGH v3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H 2 metrics

VRT selects the newest version's highest entry and publishes it as cvssScore, newest rather than largest because scores are not comparable across versions, and highest rather than first because the first entry is frequently a CNA placeholder scoring 0.0 over NVD's own analysis.

Version Score Band Vector Assigner Type

CVSS 3.0 7.5 HIGH CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H NVD Primary published

CVSS 2.0 5.0 no band published AV:N/AC:L/Au:N/C:N/I:N/A:P NVD Primary

Version	Score	Band	Vector	Assigner	Type
CVSS 3.0	7.5	HIGH	`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`	NVD	Primary	published
CVSS 2.0	5.0	no band published	`AV:N/AC:L/Au:N/C:N/I:N/A:P`	NVD	Primary

Affected Software & Releases

☕ Maven Library Packages

Artifact coordinates and fix boundaries from OSV.dev

Package Coordinate Introduced Fixed Last affected

org.apache.mesos:mesos 0 1.1.3 unbounded

org.apache.mesos:mesos 1.2.0 1.2.2 unbounded

org.apache.mesos:mesos 1.3.0 1.3.1 unbounded

Package Coordinate	Introduced	Fixed	Last affected
`org.apache.mesos:mesos`	0	`1.1.3`	unbounded
`org.apache.mesos:mesos`	1.2.0	`1.2.2`	unbounded
`org.apache.mesos:mesos`	1.3.0	`1.3.1`	unbounded

🖥️ Product CPEs & Version Ranges

2 product(s) over 9 version claims (uncapped)

Source	Vendor	Product	Scheme	Affected Versions
nvd	apache	mesos	generic	≤ 1.1.2 · 1.2.0 · 1.2.1 · 1.3.0 · 1.3.1 · 1.4.0-dev
osv	org.apache.mesos	mesos	generic	＜ 1.1.3 · ≥ 1.2.0 and ＜ 1.2.2 · ≥ 1.3.0 and ＜ 1.3.1

Source

Vendor

Product

Scheme

Affected Versions

nvd

apache

mesos

generic

≤ 1.1.2 · 1.2.0 · 1.2.1 · 1.3.0 · 1.3.1 · 1.4.0-dev

osv

org.apache.mesos

mesos

generic

＜ 1.1.3 · ≥ 1.2.0 and ＜ 1.2.2 · ≥ 1.3.0 and ＜ 1.3.1

References

URL	Tags
https://lists.apache.org/thread.html/cc1e7a69ea78da0511f5b54b6be7aa6e3c78edad5aaff430e7de028b@%3Cdev.mesos.apache.org%3E	WEB
http://www.securityfocus.com/bid/101023	WEB
https://lists.apache.org/thread.html/cc1e7a69ea78da0511f5b54b6be7aa6e3c78edad5aaff430e7de028b%40%3Cdev.mesos.apache.org%3E

URL

Timeline

Published 2017-09-29 Last modified 2026-06-17

Published	2017-09-29	By the CVE Program.
NVD record modified	2026-06-17	NVD's own last-modified date for this record.

Published

2017-09-29

By the CVE Program.

NVD record modified

2026-06-17

NVD's own last-modified date for this record.

Pipeline policy audit (15 of 21 rules evaluated)

15 of 21 rules ran. The rest were never reached, because an earlier stage settled the CVE, a distinct claim from a rule that ran and found nothing.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? first match wins

1 rejected no-match CVE Program withdrawal of this identifier

scope: Is the vulnerability ARMR's to address? first match wins

2 armr-patch-file no-match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no-match An ARMR security-rule template on disk for this CVE

4 manual-classification no-match A researcher's recorded decision for this specific CVE

5 manual classification no-match Manual classification of this CVE in the legacy dataset

6 non-java-upstream no-match A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component no-match The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the native WebLogic proxy plug-in. Oracle gives these no CPE of their own and names them only in the description.

8 osv-maven matched Queued for review Maven packages: org.apache.mesos:mesos

9 cna-maven-package not-reached An affected Maven artifact named by the CNA itself

10 known-cpe-product not-reached An NVD CPE naming a product ARMR tracks

11 cna-cpe-product not-reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

12 oracle-advisory-family not-reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

13 non-deployable-product not-reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

14 unmatched-product not-reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? cumulative: every rule gets a turn

15 patch-hint no-match A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

16 open-source-maven matched Mitigation candidate Open-source Maven artifact indexed by OSV (Maven packages: org.apache.mesos:mesos). The source is public, which makes an ARMR patch rule a candidate; nothing here establishes that one can be written.

17 poc-derivable skipped An indexed exploit to reverse-engineer, where there is no source to read

18 no-exploit skipped With no fix path, a public exploit, or a CISA record of one

19 secure-rule-match no-match A vulnerability class already blocked by an ARMR security rule

20 below-action-threshold no-match Severity is HIGH — only MEDIUM/LOW are deprioritized

21 no-exploit-published decided it matched No exploit published No working exploit has been published, and an upstream fix path does exist, so the remediation half of the candidacy still holds.

What the scope rules read

The products the record named, and whether known-products.yaml tracks them. This is the evidence the scope stage decided on.

Vendor Product Tracked CPE Source

apache mesos not tracked cpe:2.3:a:apache:mesos:*:*:*:*:*:*:*:*

Raw stored JSON document for this CVE ↗ · NVD ↗ · CVE.org ↗