The remote Oracle Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2023-2859 advisory.

  - Git is a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4,     2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An     unsuspecting user could still be affected by the issue reported in CVE-2022-24765, for example when     navigating as root into a shared tmp directory that is owned by them, but where an attacker could create a     git repository. Versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 contain a     patch for this issue. The simplest way to avoid being affected by the exploit described in the example is     to avoid running git as root (or an Administrator in Windows), and if needed to reduce its use to a     minimum. While a generic workaround is not possible, a system could be hardened from the exploit described     in the example by removing any such repository if it exists already and creating one as root to block any     future attacks. (CVE-2022-29187)

  - Git is an open source, scalable, distributed revision control system. `git shell` is a restricted login     shell that can be used to implement Git's push/pull functionality via SSH. In versions prior to 2.30.6,     2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4, the function that splits the command arguments     into an array improperly uses an `int` to represent the number of entries in the array, allowing a     malicious actor to intentionally overflow the return value, leading to arbitrary heap writes. Because the     resulting array is then passed to `execv()`, it is possible to leverage this attack to gain remote code     execution on a victim machine. Note that a victim must first allow access to `git shell` as a login shell     in order to be vulnerable to this attack. This problem is patched in versions 2.30.6, 2.31.5, 2.32.4,     2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 and users are advised to upgrade to the latest version.
    Disabling `git shell` access via remote logins is a viable short-term workaround. (CVE-2022-39260)

  - Git for Windows is a fork of Git containing Windows-specific patches. This vulnerability affects users     working on multi-user machines, where untrusted parties have write access to the same hard disk. Those     untrusted parties could create the folder `C:\.git`, which would be picked up by Git operations run     supposedly outside a repository while searching for a Git directory. Git would then respect any config in     said Git directory. Git Bash users who set `GIT_PS1_SHOWDIRTYSTATE` are vulnerable as well. Users who     installed posh-gitare vulnerable simply by starting a PowerShell. Users of IDEs such as Visual Studio are     vulnerable: simply creating a new project would already read and respect the config specified in     `C:\.git\config`. Users of the Microsoft fork of Git are vulnerable simply by starting a Git Bash. The     problem has been patched in Git for Windows v2.35.2. Users unable to upgrade may create the folder `.git`     on all drives where Git commands are run, and remove read/write access from those folders as a workaround.
    Alternatively, define or extend `GIT_CEILING_DIRECTORIES` to cover the _parent_ directory of the user     profile, e.g. `C:\Users` if the user profile is located in `C:\Users\my-user-name`. (CVE-2022-24765)

  - Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5,     2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a     malicious actor. When performing a local clone (where the source and target of the clone are on the same     volume), Git copies the contents of the source's `$GIT_DIR/objects` directory into the destination by     either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via `--no-     hardlinks`). A malicious actor could convince a victim to clone a repository with a symbolic link pointing     at sensitive information on the victim's machine. This can be done either by having the victim clone a     malicious repository on the same machine, or having them clone a malicious repository embedded as a bare     repository via a submodule from any source, provided they clone with the `--recurse-submodules` option.
    Git does not create symbolic links in the `$GIT_DIR/objects` directory. The problem has been patched in     the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning     untrusted repositories using the `--local` optimization when on a shared machine, either by passing the     `--no-local` option to `git clone` or cloning from a URL that uses the `file://` scheme. Alternatively,     avoid cloning repositories from untrusted sources with `--recurse-submodules` or run `git config --global     protocol.file.allow user`. (CVE-2022-39253)

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

Detections

Analytics

Oracle Linux 8 : git (ELSA-2023-2859)

high Nessus Plugin ID 176292

Version 1.1

Version 1.0

Version 1.1 Oct 23, 2024, 5:25 AM CVSS metrics ("Cvssv4 score" set to 0.0) CVSS temporal metrics ("CVSSv2 temporal vector" set to "CVSS2#E:U/RL:OF/RC:C") CVSS temporal metrics ("CVSSv3 temporal vector" set to "CVSS:3.0/E:U/RL:O/RC:C") CVSSv2 severity (based on None, severity decreased from "High" to "Low") Detection (updated detection logic) Plugin Feed: 202410230525
Version 1.0 May 24, 2023, 4:08 PM New Plugin Feed: 202305241608