-
Notifications
You must be signed in to change notification settings - Fork 3.3k
{AFD} Bug fix for Binding a socket to all network interfaces CVE-2018-1281 #31492
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
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
|
Thank you for your contribution @odaysec! We will review the pull request and get back to you soon. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
azure-cli/src/azure-cli/azure/cli/command_modules/batchai/custom.py
Line 1027 in a4c9d4d
fix the issue the socket should be bound to a specific interface, such as
127.0.0.1(localhost), instead of all interfaces. This ensures that the socket is only accessible locally and not exposed to external networks. The change should be made in the_get_available_local_portfunction, specifically on line 1027 where thebindmethod is called.This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.