Joegardner20 opened a new issue, #16742:
URL: https://github.com/apache/dolphinscheduler/issues/16742

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   **Issue Description**: 
   During the setup of the _DolphinScheduler_ project, I encountered a security 
vulnerability in the GitPython dependency listed in 
dolphinscheduler/tools/release/requirements.txt. The current version 
constraint, **GitPython~=3.1**, includes versions of GitPython that are 
affected by 
[CVE-2024-22190](https://github.com/advisories/GHSA-2mqj-m65w-jghx). 
   
   **Vulnerable Version**:
   •    GitPython: Versions < 3.1.41 are affected by this vulnerability.
   
   **Suggested Resolution**: 
   To mitigate this issue, please update the version of GitPython to **3.1.41** 
or later in the requirements.txt file.
   
   ### What you expected to happen
   
   fix this vulnerability
   
   ### How to reproduce
   
   Install the current version of DolphinScheduler following the standard setup 
guide. Ensure that the GitPython dependency is installed according to the 
version constraint specified in dolphinscheduler/tools/release/requirements.txt 
(i.e., GitPython~=3.1). This setup introduces the CVE-2024-22190 vulnerability, 
as it allows installation of GitPython versions below 3.1.41, which are 
affected by this security issue.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.2.x
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to