What is CVE-2019-11779?A medium-severity flaw in Mosquitto, explained.
CVE-2019-11779 is a medium-severity flaw (CVSS 6.5) in Mosquitto from Eclipse, published on 19 September 2019. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 2.7%. If you run an affected version, plan in the vendor’s fix.
Published 19 September 2019. Record last updated 7 November 2023. We keep this page's data up to date.
What is CVE-2019-11779? In plain terms.
It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can take it offline.
In Eclipse Mosquitto 1.5.0 to 1.6.5 inclusive, if a malicious MQTT client sends a SUBSCRIBE packet containing a topic that consists of approximately 65400 or more '/' characters, i.e. the topic hierarchy separator, then a stack overflow will occur.
What kind of flaw is it?
- CWE-674Uncontrolled Recursion
- CWE-754Improper Check for Unusual or Exceptional Conditions
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstAn ordinary user account
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan take it offline
Severity vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is CVE-2019-11779 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.7%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
- Exploit likelihood jumped
- Exploit likelihood fell
CVE-2019-11779 scores 27. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2019-11779 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2019-11779? 6 products.
The published record lists 6 products from 5 vendors. Versions are shown as published: "1.5 to before 1.5.9" means from 1.5 up to, but not including, 1.5.9. If you run one of these, check your version, then go to the fix below.
- Application
Mosquitto
by Eclipse
Affected versions1.5 to before 1.5.91.6 to before 1.6.6 - Operating system
Fedora
Affected versions293031 - Operating system
Debian Linux
by Debian
Affected versions8.010.0 - Application
Backports Sle
by Opensuse
Affected versions15.0-sp1 - Operating system
Leap
by Opensuse
Affected versions15.1 - Operating system
Ubuntu Linux
by Canonical
Affected versions19.04
How do I fix CVE-2019-11779? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
10 links- Show Bug.cgi (opens in a new tab)eclipse.org
- Msg00077 (opens in a new tab)opensuse.org · 2019
- Msg00008 (opens in a new tab)opensuse.org · 2019
- Msg00035 (opens in a new tab)debian.org · 2019
- D4WMHIM64Q35NGTR6R3ILZUL4MA4ANB5 (opens in a new tab)fedoraproject.org
- HFWQBNFTAVHPUYNGYO2TCPF5PCSWC2Z7 (opens in a new tab)fedoraproject.org
Does CVE-2019-11779 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
In Eclipse Mosquitto 1.5.0 to 1.6.5 inclusive, if a malicious MQTT client sends a SUBSCRIBE packet containing a topic that consists of approximately 65400 or...
- Matched to
- Mosquitto on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2019-11779 is a medium-severity flaw in Mosquitto from Eclipse, published on 19 September 2019. It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can take it offline.
It scores 6.5 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2019-11779 is 27 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 2.7%. That can change at any time, which is why we keep watching.
For Mosquitto from Eclipse: 1.5 to before 1.5.9, 1.6 to before 1.6.6. The record lists 6 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.