The Microsoft Visual Studio Products are missing security updates. It is, therefore, affected by multiple vulnerabilities:

  - A remote code execution vulnerability in the MSDIA SDK where corrupted PDBs can cause heap overflow,     leading to a crash or remote code execution. (CVE-2023-24897)

  - A remote code execution vulnerability where specially crafted input to git apply -reject can lead to     controlled content writes at arbitrary locations. (CVE-2023-25652)

  - A spoofing vulnerability where Github localization messages refer to a hard-coded path instead of     respecting the runtime prefix that leads to out-of-bound memory writes and crashes. (CVE-2023-25815)

  - An Out-Of-Bounds Write Vulnerability in Autodesk FBX SDK version 2020 or prior may lead to code     execution through maliciously crafted FBX files or information disclosure. (CVE-2023-27909)

  - An information disclosure vulnerability where a user may be tricked into opening a malicious     FBX file. This may exploit a stack buffer overflow (CVE-2023-27910) or heap buffer overflow     (CVE-2023-27911) vulnerability in Autodesk FBX SDK 2020 or prior which may lead to remote code     execution. 

  - A remote code execution vulnerability where a configuration file containing a logic error results     in arbitrary configuration injection. (CVE-2023-29007)

  - A remote code execution vulnerability where the Git for Windows executable responsible for     implementing a SOCKS5 proxy is susceptible to picking up an untrusted configuration on multi-user     machines. (CVE-2023-29011)

  - A remote code execution vulnerability where the Git for Windows Git CMD program incorrectly     searches for a program upon startup, leading to silent arbitrary code execution. (CVE-2023-29012)

  - A remote code execution vulnerability in the .NET SDK during tool restore which can lead to an     elevation of privilege. (CVE-2023-33135)

  - An information disclosure vulnerability by the obj file parser in Visual Studio. (CVE-2023-33139)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

According to the versions of the git packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

  - Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8,     2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to `git apply --reject`, a     path outside the working tree can be overwritten with partially controlled contents (corresponding to the     rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8,     2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using `git apply` with     `--reject` when applying patches from an untrusted source. Use `git apply --stat` to inspect a patch     before applying; avoid applying one that create a conflict where a link corresponding to the `*.rej` file     exists. (CVE-2023-25652)

  - In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a     consequence, Git is expected not to localize messages at all, and skips the gettext initialization.
    However, due to a change in MINGW-packages, the `gettext()` function's implicit initialization no longer     uses the runtime prefix but uses the hard-coded path `C:\mingw64\share\locale` to look for localized     messages. And since any authenticated user has the permission to create folders in `C:\` (and since     `C:\mingw64` does not typically exist), it is possible for low-privilege users to place fake messages in     that location where `git.exe` will pick them up in version 2.40.1. This vulnerability is relatively hard     to exploit and requires social engineering. For example, a legitimate message at the end of a clone could     be maliciously modified to ask the user to direct their web browser to a malicious website, and the user     might think that the message comes from Git and is legitimate. It does require local write access by the     attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this     issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or     alternatively create a `C:\mingw64` folder and leave it empty. Users who have administrative rights may     remove the permission to create folders in `C:\`. (CVE-2023-25815)

  - Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8,     2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, a specially crafted `.gitmodules` file with submodule URLs     that are longer than 1024 characters can used to exploit a bug in     `config.c::git_config_copy_or_rename_section_in_file()`. This bug can be used to inject arbitrary     configuration into a user's `$GIT_DIR/config` when attempting to remove the configuration section     associated with that submodule. When the attacker injects configuration values which specify executables     to run (such as `core.pager`, `core.editor`, `core.sshCommand`, etc.) this can lead to a remote code     execution. A fix A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6,     2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid running `git submodule deinit` on untrusted     repositories or without prior inspection of any submodule sections in `$GIT_DIR/config`. (CVE-2023-29007)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

According to the versions of the git packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8,     2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to `git apply --reject`, a     path outside the working tree can be overwritten with partially controlled contents (corresponding to the     rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8,     2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using `git apply` with     `--reject` when applying patches from an untrusted source. Use `git apply --stat` to inspect a patch     before applying; avoid applying one that create a conflict where a link corresponding to the `*.rej` file     exists. (CVE-2023-25652)

  - In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a     consequence, Git is expected not to localize messages at all, and skips the gettext initialization.
    However, due to a change in MINGW-packages, the `gettext()` function's implicit initialization no longer     uses the runtime prefix but uses the hard-coded path `C:\mingw64\share\locale` to look for localized     messages. And since any authenticated user has the permission to create folders in `C:\` (and since     `C:\mingw64` does not typically exist), it is possible for low-privilege users to place fake messages in     that location where `git.exe` will pick them up in version 2.40.1. This vulnerability is relatively hard     to exploit and requires social engineering. For example, a legitimate message at the end of a clone could     be maliciously modified to ask the user to direct their web browser to a malicious website, and the user     might think that the message comes from Git and is legitimate. It does require local write access by the     attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this     issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or     alternatively create a `C:\mingw64` folder and leave it empty. Users who have administrative rights may     remove the permission to create folders in `C:\`. (CVE-2023-25815)

  - Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8,     2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, a specially crafted `.gitmodules` file with submodule URLs     that are longer than 1024 characters can used to exploit a bug in     `config.c::git_config_copy_or_rename_section_in_file()`. This bug can be used to inject arbitrary     configuration into a user's `$GIT_DIR/config` when attempting to remove the configuration section     associated with that submodule. When the attacker injects configuration values which specify executables     to run (such as `core.pager`, `core.editor`, `core.sshCommand`, etc.) this can lead to a remote code     execution. A fix A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6,     2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid running `git submodule deinit` on untrusted     repositories or without prior inspection of any submodule sections in `$GIT_DIR/config`. (CVE-2023-29007)

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Published	Updated	Severity
177249	Security Updates for Microsoft Visual Studio Products (June 2023)	Nessus	Windows : Microsoft Bulletins	6/13/2023	1/10/2024	high
178084	EulerOS 2.0 SP9 : git (EulerOS-SA-2023-2332)	Nessus	Huawei Local Security Checks	7/9/2023	7/9/2023	high
188717	EulerOS 2.0 SP11 : git (EulerOS-SA-2023-2683)	Nessus	Huawei Local Security Checks	1/16/2024	1/16/2024	high
188835	EulerOS Virtualization 3.0.6.6 : git (EulerOS-SA-2023-3398)	Nessus	Huawei Local Security Checks	1/16/2024	1/16/2024	high

Detections

Analytics

Plugins Search

high

high

high

high