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

[QUERY] Azure.Security.KeyVault.Secrets - latest Package uses outdated System.Text.Json 6.0.10 #48219

Open
oliverabrahamserrala opened this issue Feb 11, 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. KeyVault question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@oliverabrahamserrala
Copy link

Library name and version

Azure.Security.KeyVault.Secrets

Query/Question

Mend reports System.Text.Json having a known vulnerability [CVE-2024-43485].
Can you please update to the latest version?

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. KeyVault 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 labels Feb 11, 2025
Copy link

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

@jsquire
Copy link
Member

jsquire commented Feb 11, 2025

Hi @oliverabrahamserrala. There is no vulnerability in the 6.0.10 version of System.Text.Json. As you'll note in that CVE, 6.0.10 is explicitly called out as a patched version, and the vulnerable range identified as >= 6.0.0, <= 6.0.9.

The Azure SDK packages are currently based on the 6.x line of BCL dependency packages, by design. Our dependencies are managed very deliberately, as we have a need to maintain compatibility across a wide variety of runtime environments, some of which have strict requirements. For example, Azure Functions and Azure PowerShell both have built-in package sets with versions we cannot exceed. We are in the process of migrating to the 8.x line, which requires extensive testing, so not likely to hit until at least April. We have no plans to move to the 9.x range, as we align with the packages from the latest LTS.

That all said, the version of System.Text.Json referenced by the Azure SDK packages does not constrain the version that you're able to use. By taking a direct reference to System.Text.Json in your application, the version used by all of your dependencies will be hoisted to match. For example, taking a direct reference on v9.0.1 in your application would cause that version to be used by KeyVault, as you're asking.

@jsquire jsquire added the issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. label Feb 11, 2025
Copy link

Hi @oliverabrahamserrala. 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.

@github-actions github-actions bot removed the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Feb 11, 2025
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. KeyVault question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
Status: Untriaged
Development

No branches or pull requests

3 participants