Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← 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.

Lifecycle evidence status

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2018-5105 11 Jun 2018 unspecified < 58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-5101 11 Jun 2018 unspecified < 58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-5100 11 Jun 2018 unspecified < 58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-5094 11 Jun 2018 unspecified < 58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-5093 11 Jun 2018 unspecified < 58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-5092 11 Jun 2018 unspecified < 58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-5090 11 Jun 2018 unspecified < 58 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7844 11 Jun 2018 unspecified < 57.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7842 11 Jun 2018 unspecified < 57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7840 11 Jun 2018 unspecified < 57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7839 11 Jun 2018 unspecified < 57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7838 11 Jun 2018 unspecified < 57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7837 11 Jun 2018 unspecified < 57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7836 11 Jun 2018 unspecified < 57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7835 11 Jun 2018 unspecified < 57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7834 11 Jun 2018 unspecified < 57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7833 11 Jun 2018 unspecified < 57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7832 11 Jun 2018 unspecified < 57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7831 11 Jun 2018 unspecified < 57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7830 11 Jun 2018 unspecified < 57; unspecified < 52.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7828 11 Jun 2018 unspecified < 57; unspecified < 52.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7827 11 Jun 2018 unspecified < 57 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7826 11 Jun 2018 unspecified < 57; unspecified < 52.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7825 11 Jun 2018 unspecified < 56; unspecified < 52.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7824 11 Jun 2018 unspecified < 56; unspecified < 52.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7823 11 Jun 2018 unspecified < 56; unspecified < 52.4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2017-7822 11 Jun 2018 unspecified < 56 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7821 11 Jun 2018 unspecified < 56 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7820 11 Jun 2018 unspecified < 56 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7819 11 Jun 2018 unspecified < 56; unspecified < 52.4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2017-7818 11 Jun 2018 unspecified < 56; unspecified < 52.4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2017-7817 11 Jun 2018 unspecified < 56 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7816 11 Jun 2018 unspecified < 56 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7815 11 Jun 2018 unspecified < 56 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7814 11 Jun 2018 unspecified < 56; unspecified < 52.4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2017-7813 11 Jun 2018 unspecified < 56 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7812 11 Jun 2018 unspecified < 56 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7811 11 Jun 2018 unspecified < 56 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7810 11 Jun 2018 unspecified < 56; unspecified < 52.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7808 11 Jun 2018 unspecified < 55 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2017-7806 11 Jun 2018 unspecified < 55 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2017-7805 11 Jun 2018 unspecified < 56; unspecified < 52.4 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2017-7799 11 Jun 2018 unspecified < 55 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7797 11 Jun 2018 unspecified < 55 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2017-7796 11 Jun 2018 unspecified < 55 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2017-7794 11 Jun 2018 unspecified < 55 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7793 11 Jun 2018 unspecified < 56; unspecified < 52.4 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2017-7790 11 Jun 2018 unspecified < 55 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7789 11 Jun 2018 unspecified < 55 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-7788 11 Jun 2018 unspecified < 55 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.