Skip to content

Upgrade to xmlsec 3.0.3. #1384

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed

Conversation

ThanksForAllTheFish
Copy link
Contributor

xmlsec is affected by CVE-2023-44483, until version 3.0.3

@pivotal-cla
Copy link

@ThanksForAllTheFish Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@pivotal-cla
Copy link

@ThanksForAllTheFish Thank you for signing the Contributor License Agreement!

@gregturn gregturn self-assigned this Oct 23, 2023
@gregturn gregturn added this to the 4.0.7 milestone Oct 23, 2023
@gregturn gregturn changed the title Fix CVE-2023-44483 Upgrade to xmlsec 3.0.3. Oct 23, 2023
@gregturn gregturn closed this in 980f917 Oct 23, 2023
@gregturn
Copy link
Contributor

Thanks @ThanksForAllTheFish. Since this is a 3rd party dependency, you can easily upgrade your own application immediately by adjusting xmlsec.version to 3.0.3.

@ThanksForAllTheFish
Copy link
Contributor Author

Thanks @ThanksForAllTheFish. Since this is a 3rd party dependency, you can easily upgrade your own application immediately by adjusting xmlsec.version to 3.0.3.

@gregturn thanks for the hint, I already upgraded the version in our app but just thought it was helpful to do this small MR

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
type: dependency-upgrade A dependency upgrade
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants