Sentrifugo
Sentrifugo
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-2024-29879 | 21 Mar 2024 | 3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29878 | 21 Mar 2024 | 3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29877 | 21 Mar 2024 | 3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29876 | 21 Mar 2024 | 3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29875 | 21 Mar 2024 | 3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29874 | 21 Mar 2024 | 3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29873 | 21 Mar 2024 | 3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29872 | 21 Mar 2024 | 3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29871 | 21 Mar 2024 | 3.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29870 | 21 Mar 2024 | 3.2 | 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.