{"vulnerability": "CVE-2023-40590", "sightings": [{"uuid": "71ae5db9-39d7-4890-abbe-34ba3514840f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-40590", "type": "seen", "source": "https://t.me/arpsyndicate/2920", "content": "#ExploitObserverAlert\n\nCVE-2024-22190\n\nDESCRIPTION: Exploit Observer has 3 entries in 2 file formats related to CVE-2024-22190. GitPython is a python library used to interact with Git repositories. There is an incomplete fix for CVE-2023-40590. On Windows, GitPython uses an untrusted search path if it uses a shell to run `git`, as well as when it runs `bash.exe` to interpret hooks. If either of those features are used on Windows, a malicious `git.exe` or `bash.exe` may be run from an untrusted repository. This issue has been patched in version 3.1.41.\n\nFIRST-EPSS: 0.000450000\nNVD-IS: 5.9\nNVD-ES: 1.8", "creation_timestamp": "2024-01-19T10:29:47.000000Z"}, {"uuid": "7b6cff1a-e49b-4210-a017-92add3319ac8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-40590", "type": "seen", "source": "https://t.me/cibsecurity/69311", "content": "\u203c CVE-2023-40590 \u203c\n\nGitPython is a python library used to interact with Git repositories. When resolving a program, Python/Windows look for the current working directory, and after that the PATH environment. GitPython defaults to use the `git` command, if a user runs GitPython from a repo has a `git.exe` or `git` executable, that program will be run instead of the one in the user's `PATH`. This is more of a problem on how Python interacts with Windows systems, Linux and any other OS aren't affected by this. But probably people using GitPython usually run it from the CWD of a repo. An attacker can trick a user to download a repository with a malicious `git` executable, if the user runs/imports GitPython from that directory, it allows the attacker to run any arbitrary commands. There is no fix currently available for windows users, however there are a few mitigations. 1: Default to an absolute path for the git program on Windows, like `C:\\\\Program Files\\\\Git\\\\cmd\\\\git.EXE` (default git path installation). 2: Require users to set the `GIT_PYTHON_GIT_EXECUTABLE` environment variable on Windows systems. 3: Make this problem prominent in the documentation and advise users to never run GitPython from an untrusted repo, or set the `GIT_PYTHON_GIT_EXECUTABLE` env var to an absolute path. 4: Resolve the executable manually by only looking into the `PATH` environment variable.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-08-28T22:16:57.000000Z"}, {"uuid": "26fe4d48-8706-40ce-b7a5-f6a88b09ec21", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-40590", "type": "published-proof-of-concept", "source": "https://t.me/CNArsenal/2483", "content": "https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-wfm5-v35h-vwf4\n\nhttps://github.com/gitpython-developers/GitPython/security/advisories/GHSA-2mqj-m65w-jghx\n\nCVE-2023-40590\n#github #poc #\u5206\u6790", "creation_timestamp": "2024-05-14T01:13:35.000000Z"}]}