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

[BUG] Update Azure.Core in Azure.Messaging.ServiceBus #47699

Open
kipusoep opened this issue Jan 2, 2025 · 3 comments
Open

[BUG] Update Azure.Core in Azure.Messaging.ServiceBus #47699

kipusoep opened this issue Jan 2, 2025 · 3 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Bus

Comments

@kipusoep
Copy link

kipusoep commented Jan 2, 2025

Library name and version

Azure.Messaging.ServiceBus 7.18.2

Describe the bug

I was wondering why Azure.Core still isn't updated in Azure.Messaging.ServiceBus? It requires >= 1.44.0 while 1.44.1 is referencing a newer version of System.Text.Json without the vulerability.

Expected behavior

Use a version of System.Text.Json that isn't vulnerable by updating Azure.Core

Actual behavior

The referenced version is not high enough

Reproduction Steps

Install Azure.Messaging.ServiceBus 7.18.2

Environment

No response

@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Bus labels Jan 2, 2025
Copy link

github-actions bot commented Jan 2, 2025

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@jsquire jsquire assigned jsquire and unassigned JoshLove-msft Jan 2, 2025
@jsquire
Copy link
Member

jsquire commented Jan 2, 2025

Hi @kipusoep. Thanks for reaching out and we regret that you're experiencing difficulties. Azure Service Bus does not use System.Text.Json and is not vulnerable due to the reference. If you are using functionality of System.Text.Json in your application, then bumping the version referenced by your application will hoist the version available in the environment. Likewise, if you're using another Azure library which depends on a newer version of Azure.Core or take a direct dependency within your application, the version of Core available to Service Bus will be hoisted as well.

Azure Service Bus automatically moves to the latest Azure Core version with each release. As a result, the next release will reference a newer Azure.Core.

@jsquire jsquire added the issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. label Jan 2, 2025
@github-actions github-actions bot removed the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Jan 2, 2025
Copy link

github-actions bot commented Jan 2, 2025

Hi @kipusoep. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Bus
Projects
None yet
Development

No branches or pull requests

3 participants