Rational Rhapsody Design Manager

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

CVE	Published	Affected versions	Fixed version information	Publisher evidence
CVE-2020-4691	8 Jan 2021	6.0.2; 6.0.6; 6.0.6.1; 7.0; 7.0.1; 7.0.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2020-4522	2 Sep 2020	6.0.2; 6.0.6; 6.0.6.1; 7.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2020-4445	2 Sep 2020	6.0.2; 6.0.6; 6.0.6.1; 7.0	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2020-4542	4 Aug 2020	6.0.2; 7.0	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-2020-4525	4 Aug 2020	6.0.2; 7.0	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-2020-4410	4 Aug 2020	6.0.2; 7.0	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-2020-4396	4 Aug 2020	6.0.2; 7.0	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-2019-4457	19 Feb 2020	6.0; 6.0.1; 6.0.2; 6.0.3; 6.0.4; 6.0.5; 6.0.6; 6.0.6.1	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2018-1535	19 Jul 2018	5.0; 5.0.2; 5.0.1; 6.0; 6.0.1; 6.0.2; 6.0.3; 6.0.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-1559	6 Jul 2018	6.0; 6.0.1; 6.0.2; 6.0.3; 6.0.4; 6.0.5; 5.0.x	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2017-1509	6 Jul 2018	6.0; 6.0.1; 6.0.2; 6.0.3; 6.0.4; 6.0.5; 5.0.x	No fixed version is explicitly recorded in the structured CVE data.	Update reference ↗
CVE-2017-1462	21 Feb 2018	5.0; 5.0.1; 6.0; 6.0.1; 6.0.2; 6.0.3; 6.0.4; 5.0.2	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-1287	24 Jul 2017	5.0.2; 5.0; 5.0.1; 6.0; 6.0.1; 6.0.2; 6.0.3	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-1249	24 Jul 2017	5.0.2; 5.0; 5.0.1; 6.0; 6.0.1; 6.0.2; 6.0.3	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-1245	24 Jul 2017	5.0; 5.0.1; 6.0; 6.0.1; 6.0.2; 6.0.3; 5.0.2	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-2016-8975	24 Jul 2017	5.0.2; 5.0; 5.0.1; 6.0; 6.0.1; 6.0.2; 6.0.3	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-2016-9698	8 Jun 2017	4.0.2; 4.0; 4.0.1; 4.0.3; 4.0.4; 4.0.5; 4.0.6; 5.0	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-2016-9697	20 Mar 2017	4.0.2; 3.0; 3.0.0.1; 4.0; 4.0.1; 4.0.3; 4.0.4; 4.0.5	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-2016-9696	20 Mar 2017	4.0.2; 3.0; 3.0.0.1; 4.0; 4.0.1; 4.0.3; 4.0.4; 4.0.5	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-2016-9694	20 Mar 2017	4.0.2; 3.0; 3.0.0.1; 4.0; 4.0.1; 4.0.3; 4.0.4; 4.0.5	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-2016-8973	20 Mar 2017	4.0.2; 3.0; 3.0.0.1; 4.0; 4.0.1; 4.0.3; 4.0.4; 4.0.5	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-2016-8974	23 Feb 2017	4.0.2; 3.0; 3.0.0.1; 4.0; 4.0.1; 4.0.3; 4.0.4; 4.0.5	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.