Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY6 SECURITY RECORDS

Buildroot

Buildroot

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 identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

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-2023-45842 5 Dec 2023 2023.08.1; dev commit 622698d7847 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45841 5 Dec 2023 2023.08.1; dev commit 622698d7847 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45840 5 Dec 2023 2023.08.1; dev commit 622698d7847 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45839 5 Dec 2023 2023.08.1; dev commit 622698d7847 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-45838 5 Dec 2023 2023.08.1; dev commit 622698d7847 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-2023-43608 5 Dec 2023 2023.08.1; dev commit 622698d7847 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 ↗

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.