Publisher not identified
SQLite
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2020-35527 | 1 Sep 2022 | sqlite 3.31.1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2020-35525 | 1 Sep 2022 | sqlite 3.31.1 | Update to V2.17.0 or later version | Update reference ↗ |
| CVE-2021-20227 | 23 Mar 2021 | sqlite 3.34.1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2019-8457 | 30 May 2019 | From 3.6.0 to 3.27.2 including | The problem is corrected in the following product versions: B&R Automation Studio 6.5 B&R recommends that customers apply the update at earliest convenience. The process to install updates is described in the user manual. The step to identify the installed product version is described in the user manual. | 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.