What is CVE-2018-11567?A low-severity flaw in Echo, explained.

Low severity10 affected products
The short answer

CVE-2018-11567 is a low-severity flaw (CVSS 3.3) in Echo from Amazon, published on 30 May 2018. 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 1.1%. If you run an affected version, plan in the vendor’s fix.

Published 30 May 2018. Record last updated 5 August 2024. We keep this page's data up to date.

What it does

What is CVE-2018-11567? In plain terms.

An attacker has to be already on the device without logging in, but a person has to take an action first. If it works, the attacker can read some data.

The official description

Prior to 2018-04-27, the reprompt feature in Amazon Echo devices could be misused by a custom Alexa skill. The reprompt feature is designed so that if Alexa does not receive an input within 8 seconds, the device can speak a reprompt, then wait an additional 8 seconds for input; if the user still does not respond, the microphone is then turned off. The vulnerability involves empty output-speech reprompts, custom wildcard ("gibberish") input slots, and logging of detected speech. If a maliciously designed skill is installed, an attacker could obtain transcripts of speech not intended for Alexa to process, but simply spoken within the device's hearing range. NOTE: The vendor states "Customer trust is important to us and we take security and privacy seriously. We have put mitigations in place for detecting this type of skill behavior and reject or suppress those skills when we do. Customers do not need to take any action for these mitigations to work.

What kind of flaw is it?

  • CWE-384Session Fixation
CVSS 3.0 scoreLow · 3.3

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAlready on the device
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstNo login needed
  • Does someone have to clickYes, a person has to take an action
  • What an attacker getsCan read some data

Severity vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Exploitation

Is CVE-2018-11567 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 1.1%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days1.1%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
How EdgeProtect ranks it
35out of 100Low

CVE-2018-11567 scores 35. 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 isKey context
  • Real threat activity around itKey context

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2018-11567 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2018-11567? 10 products.

The published record lists 10 products from 1 vendor. Versions are shown as published: "before 2018-04-27" means every version up to, but not including, 2018-04-27. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2018-11567? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? EdgeProtect can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the latest update from the vendor. The references list where the vendor has published details.
  3. 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.
  4. 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.
EdgeProtect

Does CVE-2018-11567 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2018-11567 is a low-severity flaw in Echo from Amazon, published on 30 May 2018. An attacker has to be already on the device without logging in, but a person has to take an action first. If it works, the attacker can read some data.

It scores 3.3 out of 10 on the CVSS severity scale, which is low. Our risk score for CVE-2018-11567 is 35 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 1.1%. That can change at any time, which is why we keep watching.

For Echo from Amazon: version not specified. The record lists 10 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.