How many CVEs have patched py_where?

1 published CVEs changed py_where in gitpython-developers/GitPython, in 2 distinct patches totalling 11 changed lines, between 2024 and 2024.

What is the latest CVE that changed py_where?

CVE-2024-22190 (Untrusted search path under some conditions on Windows allows arbitrary code execution), published 2024-01-11, changed lines 330 to 340 of git/util.py.

How does py_where compare to the rest of gitpython-developers/GitPython?

gitpython-developers/GitPython has 18 CVEs with a located fix in total; 1 of them changed py_where.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

gitpython-developers/GitPython

Function

py_where

Name: py_where in gitpython-developers/GitPython: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

git/util.py

Last patched January 11, 2024

1

CVEs

That changed this function

2

Distinct patches

Backports counted once

11

Lines changed

Added plus removed

2024

Years

By CVE publication date

Overview

py_where in gitpython-developers/GitPython was changed by 1 published CVE fixes in 2024, in 2 distinct patches that added or removed 11 lines in total.

gitpython-developers/GitPython has 18 CVEs with a located fix in total, so 6% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed py_where, newest first, with the lines each fix touched.

Untrusted search path under some conditions on Windows allows arbitrary code execution
CVE-2024-22190 · lines 330–340 · +11 −0
High · CVSS 8.6
EPSS 0.3%2024-01-11

Get an alert when the next CVE fix lands in gitpython-developers/GitPython, with the patched functions.

Monitor GitPython CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in gitpython-developers/GitPython changed by the most CVE fixes.

_clone4 CVEs · git/repo/base.py execute2 CVEs · git/cmd.py blame_incremental2 CVEs · git/repo/base.py ls_remote2 CVEs · git/cmd.py check_unsafe_options2 CVEs · git/cmd.py blame2 CVEs · git/repo/base.py

All patched functions in gitpython-developers/GitPython

Frequently asked questions

Common questions about CVE fixes to py_where.

How many CVEs have patched py_where?: 1 published CVEs changed py_where in gitpython-developers/GitPython, in 2 distinct patches totalling 11 changed lines, between 2024 and 2024.
What is the latest CVE that changed py_where?: CVE-2024-22190 (Untrusted search path under some conditions on Windows allows arbitrary code execution), published 2024-01-11, changed lines 330 to 340 of git/util.py.
How does py_where compare to the rest of gitpython-developers/GitPython?: gitpython-developers/GitPython has 18 CVEs with a located fix in total; 1 of them changed py_where.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track gitpython-developers/GitPython CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing