Page 7 of 49 results (0.005 seconds)

CVSS: 9.8EPSS: 2%CPEs: 1EXPL: 1

The async-git package before 1.13.2 for Node.js allows OS Command Injection via shell metacharacters, as demonstrated by git.reset and git.tag. El paquete async-git versiones anteriores a 1.13.2 para Node.js, permite una Inyección de Comandos del Sistema Operativo por medio de metacaracteres de shell, como es demostrado por git.reset y git.tag • https://advisory.checkmarx.net/advisory/CX-2021-4772 https://github.com/omrilotan/async-git/pull/13 https://github.com/omrilotan/async-git/pull/13/commits/611823bd97dd41e9e8127c38066868ff9dcfa57a https://github.com/omrilotan/async-git/pull/13/commits/a5f45f58941006c4cc1699609383b533d9b92c6a https://github.com/omrilotan/async-git/pull/14 • CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') •

CVSS: 7.8EPSS: 0%CPEs: 1EXPL: 0

Git LFS is a command line extension for managing large files with Git. On Windows, if Git LFS operates on a malicious repository with a git.bat or git.exe file in the current directory, that program would be executed, permitting the attacker to execute arbitrary code. This does not affect Unix systems. This is the result of an incomplete fix for CVE-2020-27955. This issue occurs because on Windows, Go includes (and prefers) the current directory when the name of a command run does not contain a directory separator. • https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-27955 https://github.com/git-lfs/git-lfs/commit/fc664697ed2c2081ee9633010de0a7f9debea72a https://github.com/git-lfs/git-lfs/releases/tag/v2.13.2 https://github.com/git-lfs/git-lfs/security/advisories/GHSA-cx3w-xqmc-84g5 • CWE-426: Untrusted Search Path •

CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 0

git-big-picture before 1.0.0 mishandles ' characters in a branch name, leading to code execution. git-big-picture versiones anteriores a 1.0.0, maneja inapropiadamente los caracteres en un nombre de rama, conllevando a una ejecución de código. • https://github.com/git-big-picture/git-big-picture/pull/27 https://github.com/git-big-picture/git-big-picture/pull/62 https://github.com/git-big-picture/git-big-picture/releases/tag/v1.0.0 • CWE-20: Improper Input Validation •

CVSS: 10.0EPSS: 95%CPEs: 1EXPL: 20

Git LFS 2.12.0 allows Remote Code Execution. Git LFS versión 2.12.0, permite una ejecución de código remota • https://github.com/ExploitBox/git-lfs-RCE-exploit-CVE-2020-27955 https://github.com/ExploitBox/git-lfs-RCE-exploit-CVE-2020-27955-Go https://github.com/r00t4dm/CVE-2020-27955 https://github.com/DeeLMind/CVE-2020-27955-LFS https://github.com/HK69s/CVE-2020-27955 https://github.com/NeoDarwin/CVE-2020-27955 https://github.com/FrostsaberX/CVE-2020-27955 https://github.com/IanSmith123/CVE-2020-27955 https://github.com/Arnoldqqq/CVE-2020-27955 https://github.com/nob0dy-3389& • CWE-427: Uncontrolled Search Path Element •

CVSS: 9.6EPSS: 0%CPEs: 1EXPL: 0

In the git-tag-annotation-action (open source GitHub Action) before version 1.0.1, an attacker can execute arbitrary (*) shell commands if they can control the value of [the `tag` input] or manage to alter the value of [the `GITHUB_REF` environment variable]. The problem has been patched in version 1.0.1. If you don't use the `tag` input you are most likely safe. The `GITHUB_REF` environment variable is protected by the GitHub Actions environment so attacks from there should be impossible. If you must use the `tag` input and cannot upgrade to `> 1.0.0` make sure that the value is not controlled by another Action. • https://github.com/ericcornelissen/git-tag-annotation-action/commit/9f30756375cc4b1b6c66f274fc9c591fa901455a https://github.com/ericcornelissen/git-tag-annotation-action/releases/tag/v1.0.1 https://github.com/ericcornelissen/git-tag-annotation-action/security/advisories/GHSA-hgx2-4pp9-357g • CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') •