GitHub: CVE-2023-29007 Arbitrary configuration injection via `git submodule deinit`
CVE-2023-29007
Security VulnerabilityReleased: Jun 13, 2023
- Assigning CNA
- GitHub
- CVE.org link
- CVE-2023-29007
- Impact
- Remote Code Execution
- Max Severity
- Important
- Weakness
Exploitability
The following table provides an exploitability assessment for this vulnerability at the time of original publication.
- Publicly disclosed
- No
- Exploited
- No
- Exploitability assessment
- Exploitation Less Likely
FAQ
Why is this GitHub CVE included in the Security Update Guide?
The vulnerability assigned to this CVE is in MinGit software which is consumed by Microsoft Visual Studio. It is being documented in the Security Update Guide to announce that the latest builds of Visual Studio are no longer vulnerable. Please see Security Update Guide Supports CVEs Assigned by Industry Partners for more information.
Acknowledgements
- Anonymous
Security Updates
To determine the support lifecycle for your software, see the Microsoft Support Lifecycle.
Release date Descending
Product
Platform
Impact
Max Severity
Article
Download
Build Number
Jun 13, 2023
Microsoft Visual Studio 2022 version 17.6
-
Remote Code Execution
Important
- 17.6.3
Jun 13, 2023
Microsoft Visual Studio 2022 version 17.4
-
Remote Code Execution
Important
- 17.4.8
Jun 13, 2023
Microsoft Visual Studio 2022 version 17.0
-
Remote Code Execution
Important
- 17.0.22
Jun 13, 2023
Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10)
-
Remote Code Execution
Important
- 16.11.27
Jun 13, 2023
Microsoft Visual Studio 2022 version 17.2
-
Remote Code Execution
Important
- 17.2.16
Jun 13, 2023
Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8)
-
Remote Code Execution
Important
- 15.9.55
All results loaded
Loaded all 6 rows
Disclaimer
The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
Revisions
version
revisionDate
description
1.0
Jun 13, 2023
Information published.
How satisfied are you with the MSRC Security Update Guide?