← Search results
CVE-LINKED INVENTORY10 SECURITY RECORDS
Microsoft
Microsoft Visual Studio
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Microsoft Visual Studio. 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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2019-1232 | 11 Sep 2019 | 2015 Update 3; 10 for 32-bit Systems; 10 for x64-based Systems; 10 Version 1607 for 32-bit Systems; 10 Version 1607 for x64-based Systems; 10 Version 1703 for 32-bit Systems; 10 Version 1703 for x64-based Systems; 10 Version 1709 for 32-bit Systems | 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-1079 | 15 Jul 2019 | 2010 Service Pack 1; 2012 Update 5; 2013 Update 5; 2015 Update 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-2019-0727 | 16 May 2019 | 2015 Update 3; 10 for 32-bit Systems; 10 for x64-based Systems; 10 Version 1607 for 32-bit Systems; 10 Version 1607 for x64-based Systems; 10 Version 1703 for 32-bit Systems; 10 Version 1703 for x64-based Systems; 10 Version 1709 for 32-bit Systems | 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-0757 | 9 Apr 2019 | 2017 for Mac; 1.1 on .NET Core 1.0; 2.1.500 on .NET Core 2.1; 2.2.100 on .NET Core 2.2; 1.1 on .NET Core 1.1; 4.3.1; 4.4.2; 4.5.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-2019-0546 | 8 Jan 2019 | 2017 version 15.9 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2019-0537 | 8 Jan 2019 | 2010 Service Pack 1; 2012 Update 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-2018-8599 | 12 Dec 2018 | 2015 Update 3; 2017; 2017 version 15.9; (Server Core installation); 32-bit Systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems | 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-2018-8232 | 11 Jul 2018 | 2017; 2017 Version 15.7.5; 2017 Version 15.8 Preview | 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-2018-8172 | 11 Jul 2018 | 2010 Service Pack 1; 2012 Update 5; 2013 Update 5; 2015 Update 3; 2017; 2017 Version 15.7.5; 2017 Version 15.8 Preview; Service Pack 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-2018-1037 | 12 Apr 2018 | 2010 Service Pack 1; 2012 Update 5; 2013 Update 5; 2015 Update 3; 2017; 2017 Version 15.6.6; 2017 Version 15.7 Preview | 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.