Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2007-4559 Patch #1

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

TrellixVulnTeam
Copy link

Patching CVE-2007-4559

Hi, we are security researchers from the Advanced Research Center at Trellix. We have began a campaign to patch a widespread bug named CVE-2007-4559. CVE-2007-4559 is a 15 year old bug in the Python tarfile package. By using extract() or extractall() on a tarfile object without sanitizing input, a maliciously crafted .tar file could perform a directory path traversal attack. We found at least one unsantized extractall() in your codebase and are providing a patch for you via pull request. The patch essentially checks to see if all tarfile members will be extracted safely and throws an exception otherwise. We encourage you to use this patch or your own solution to secure against CVE-2007-4559. Further technical information about the vulnerability can be found in this blog.

If you have further questions you may contact us through this projects lead researcher Kasimir Schulz.

@sourcery-ai
Copy link

sourcery-ai bot commented Oct 2, 2022

Sourcery Code Quality Report

✅  Merging this PR will increase code quality in the affected files by 31.94%.

Quality metrics Before After Change
Complexity 1.00 ⭐ 1.29 ⭐ 0.29 👎
Method Length 248.00 ⛔ 50.33 ⭐ -197.67 👍
Working memory 12.00 😞 6.71 🙂 -5.29 👍
Quality 50.75% 🙂 82.69% 31.94% 👍
Other metrics Before After Change
Lines 59 29 -30
Changed files Quality Before Quality After Quality Change
src/mlops-modelbuild/pipelines/heartdisease/evaluate.py 50.75% 🙂 82.69% ⭐ 31.94% 👍

Here are some functions in these files that still need a tune-up:

File Function Complexity Length Working Memory Quality Recommendation

Legend and Explanation

The emojis denote the absolute quality of the code:

  • ⭐ excellent
  • 🙂 good
  • 😞 poor
  • ⛔ very poor

The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request.


Please see our documentation here for details on how these metrics are calculated.

We are actively working on this report - lots more documentation and extra metrics to come!

Help us improve this quality report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants