-
Notifications
You must be signed in to change notification settings - Fork 350
[Bugfix] Update aiohttp to resolve CVE-2024-23334 vulnerability #722
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
[Bugfix] Update aiohttp to resolve CVE-2024-23334 vulnerability #722
Conversation
…equirements.txt Signed-off-by: Ifta Khairul Alam Adil <ikaadil007@gmail.com>
Summary of ChangesHello @ikaadil, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request implements a critical security update by upgrading the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request aims to fix a security vulnerability (CVE-2024-23334) in aiohttp by updating its version. While updating is the correct approach, the target version 3.12.15 specified in the changes does not seem to exist for aiohttp, which would cause dependency installation to fail. I've left comments with suggestions to use the latest valid version, 3.9.5, which resolves the vulnerability.
Security Fix: aiohttp vulnerability resolvedProblemThe current aiohttp version 3.9.1 has a high-severity vulnerability CVE-2024-23334 with EPSS score of 93.6%. This was flagged by grype scanner as a critical security issue. Before the fix (main branch)grype lmcache/lmstack-router:latestFound 95 total vulnerabilities including these aiohttp issues: After the fix (this branch)grype lmcache/lmstack-router:latestResults:
No aiohttp vulnerabilities found in the scan results. Full grype output: Summary
The fix is ready for merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you use the latest stable version since you want to update it?
Ha ha. They just released a new version after my change. I am updating the version. Thanks. |
Signed-off-by: Ifta Khairul Alam Adil <ikaadil007@gmail.com>
zerofishnoodles
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…-project#722) * Update aiohttp dependency to include speedups in pyproject.toml and requirements.txt Signed-off-by: Ifta Khairul Alam Adil <ikaadil007@gmail.com> * Update aiohttp dependency to version 3.13.0 for performance improvements Signed-off-by: Ifta Khairul Alam Adil <ikaadil007@gmail.com> --------- Signed-off-by: Ifta Khairul Alam Adil <ikaadil007@gmail.com> Signed-off-by: senne.mennes@capgemini.com <senne.mennes@capgemini.com>
…equirements.txt
FILL IN THE PR DESCRIPTION HERE
FIX #714
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE
-swhen doinggit commit[Bugfix],[Feat], and[CI].Detailed Checklist (Click to Expand)
Thank you for your contribution to production-stack! Before submitting the pull request, please ensure the PR meets the following criteria. This helps us maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Please try to classify PRs for easy understanding of the type of changes. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:
[Bugfix]for bug fixes.[CI/Build]for build or continuous integration improvements.[Doc]for documentation fixes and improvements.[Feat]for new features in the cluster (e.g., autoscaling, disaggregated prefill, etc.).[Router]for changes to thevllm_router(e.g., routing algorithm, router observability, etc.).[Misc]for PRs that do not fit the above categories. Please use this sparingly.Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:
pre-committo format your code. SeeREADME.mdfor installation.DCO and Signed-off-by
When contributing changes to this project, you must agree to the DCO. Commits must include a
Signed-off-by:header which certifies agreement with the terms of the DCO.Using
-swithgit commitwill automatically add this header.What to Expect for the Reviews
We aim to address all PRs in a timely manner. If no one reviews your PR within 5 days, please @-mention one of YuhanLiu11
, Shaoting-Feng or ApostaC.