← Search results
CVE-LINKED INVENTORY1604 SECURITY RECORDS
Mozilla
Firefox
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Firefox. Use that record for publisher support phases and retirement dates.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2019-11764 | 8 Jan 2020 | before 70; before 68.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11763 | 8 Jan 2020 | before 70; before 68.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11762 | 8 Jan 2020 | before 70; before 68.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11761 | 8 Jan 2020 | before 70; before 68.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11760 | 8 Jan 2020 | before 70; before 68.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11759 | 8 Jan 2020 | before 70; before 68.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11758 | 8 Jan 2020 | before 69; before 68.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11757 | 8 Jan 2020 | before 70; before 68.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11756 | 8 Jan 2020 | before 71 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2013-1689 | 10 Dec 2019 | 20.0a1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11754 | 27 Sep 2019 | unspecified < 69.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11733 | 27 Sep 2019 | unspecified < 68.0.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11734 | 27 Sep 2019 | unspecified < 69 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11735 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11736 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11737 | 27 Sep 2019 | unspecified < 69 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11738 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11740 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1; unspecified < 60.9 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11741 | 27 Sep 2019 | unspecified < 69 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11742 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1; unspecified < 60.9 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11743 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1; unspecified < 60.9 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11744 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1; unspecified < 60.9 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11746 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1; unspecified < 60.9 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11747 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11748 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11749 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11750 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11751 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11752 | 27 Sep 2019 | unspecified < 69; unspecified < 68.1; unspecified < 60.9 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11753 | 27 Sep 2019 | unspecified < 69; unspecified < 60.9; unspecified < 68.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-9814 | 23 Jul 2019 | unspecified < 67 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-9821 | 23 Jul 2019 | unspecified < 67 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11695 | 23 Jul 2019 | unspecified < 67 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11696 | 23 Jul 2019 | unspecified < 67 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11697 | 23 Jul 2019 | unspecified < 67 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11699 | 23 Jul 2019 | unspecified < 67 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11700 | 23 Jul 2019 | unspecified < 67 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11701 | 23 Jul 2019 | unspecified < 67 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11702 | 23 Jul 2019 | unspecified < 67.0.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11710 | 23 Jul 2019 | unspecified < 68 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11714 | 23 Jul 2019 | unspecified < 68 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11716 | 23 Jul 2019 | unspecified < 68 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11718 | 23 Jul 2019 | unspecified < 68 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11720 | 23 Jul 2019 | unspecified < 68 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11721 | 23 Jul 2019 | unspecified < 68 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11723 | 23 Jul 2019 | unspecified < 68 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11724 | 23 Jul 2019 | unspecified < 68 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11725 | 23 Jul 2019 | unspecified < 68 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11727 | 23 Jul 2019 | unspecified < 68 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-11728 | 23 Jul 2019 | unspecified < 68 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.