What is CVE-2019-11730?A medium-severity flaw in Firefox, explained.
CVE-2019-11730 is a medium-severity flaw (CVSS 6.5) in Firefox from Mozilla, published on 23 July 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 20%. If you run an affected version, plan in the vendor’s fix.
Published 23 July 2019. Record last updated 31 January 2023. We keep this page's data up to date.
What is CVE-2019-11730? In plain terms.
It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read data.
A vulnerability exists where if a user opens a locally saved HTML file, this file can use file: URIs to access other files in the same directory or sub-directories if the names are known or guessed. The Fetch API can then be used to read the contents of any files stored in these directories and they may uploaded to a server. It was demonstrated that in combination with a popular Android messaging app, if a malicious HTML attachment is sent to a user and they opened that attachment in Firefox, due to that app's predictable pattern for locally-saved file names, it is possible to read attachments the victim received from other correspondents. This vulnerability affects Firefox ESR < 60.8, Firefox < 68, and Thunderbird < 60.8.
What kind of flaw is it?
- UnknownUnknown
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 firstNo login needed
- Does someone have to clickYes, a person has to take an action
- What an attacker getsCan read data
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Is CVE-2019-11730 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 20%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
- Exploit likelihood fell
CVE-2019-11730 scores 46. Action: Plan remediation.
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-11730 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-11730? 7 products.
The published record lists 7 products from 4 vendors. Versions are shown as published: "before 68.0" means every version up to, but not including, 68.0. If you run one of these, check your version, then go to the fix below.
- Application
Firefox
by Mozilla
Affected versionsbefore 68.0 - Operating system
Leap
by Opensuse
Affected versions15.015.1 - Operating system
Debian Linux
by Debian
Affected versions8.0 - Application
Firefox Esr
by Mozilla
Affected versionsbefore 60.8 - Operating system
Linux Enterprise
by Suse
Affected versions12.0 - Application
Package Hub
by Suse
Affected versionsversion not specified - Application
Thunderbird
by Mozilla
Affected versionsbefore 60.8
How do I fix CVE-2019-11730? 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 advisories and patch notes 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.
Does CVE-2019-11730 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
A vulnerability exists where if a user opens a locally saved HTML file, this file can use file: URIs to access other files in the same directory or sub-direc...
- Matched to
- Firefox 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-11730 is a medium-severity flaw in Firefox from Mozilla, published on 23 July 2019. It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read data.
It scores 6.5 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2019-11730 is 46 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
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 20%. That can change at any time, which is why we keep watching.
For Firefox from Mozilla: before 68.0. The record lists 7 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.