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

Azure CLI 2.67.0 container (mariner) is being flagged for security vulnerability and need a new version #30660

Open
ericsuhong opened this issue Jan 14, 2025 · 5 comments
Assignees
Labels
Azure CLI Team The command of the issue is owned by Azure CLI team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone

Comments

@ericsuhong
Copy link

The latest Azure CLI 2.67.0 cbl-mariner2.0 version is being flagged for security vulnerabilities (https://mcr.microsoft.com/en-us/artifact/mar/azure-cli/tags), and we need a new version.

I see that Azure CLI 2.68.0 has been released. Can we get the latest Azure CLI container version published to mcr?

Thanks.

Copy link

This issue is related to security. Please pay attention.

@yonzhan yonzhan added Azure CLI Team The command of the issue is owned by Azure CLI team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jan 14, 2025
@yonzhan yonzhan added this to the Backlog milestone Jan 14, 2025
@yonzhan
Copy link
Collaborator

yonzhan commented Jan 14, 2025

mariner

@ericsuhong
Copy link
Author

We are willing to switch to azurelinux3 if needed.

@bebound
Copy link
Contributor

bebound commented Jan 15, 2025

It's already been published to MAR: https://mcr.microsoft.com/en-us/artifact/mar/azure-cli/tags

@yonzhan
Copy link
Collaborator

yonzhan commented Jan 15, 2025

Thank you for opening this issue, we will look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure CLI Team The command of the issue is owned by Azure CLI team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

3 participants