Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Improve GHSA-h436-432x-8fvx #2855

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

wtwhite
Copy link

@wtwhite wtwhite commented Oct 15, 2023

Updates

  • Affected products

Comments
Several other components are also affected as a result of cloning (copying source code) or shading (copying source code and renaming packages). Proof-of-Vulnerability projects with tests to verify the presence of the CVE can be found here: https://github.com/jensdietrich/xshady-release/.

See #2258, especially #2258 (comment), for more details.

@github-actions github-actions bot changed the base branch from main to wtwhite/advisory-improvement-2855 October 15, 2023 23:19
@wtwhite
Copy link
Author

wtwhite commented Oct 19, 2023

@darakian Wondering if there's anything further I need to do here?

@advisory-database advisory-database bot merged commit 045f0ce into github:wtwhite/advisory-improvement-2855 Oct 31, 2023
@advisory-database
Copy link
Contributor

Hi @wtwhite! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future!

@wtwhite
Copy link
Author

wtwhite commented Nov 2, 2023

Thanks for merging this (I guess this was you @darakian?), but I noticed that the advisory page hasn't actually updated with the new affected product or the new references (though my username now appears in the credits, so something "got through"). Any ideas?

For comparison I think the advisory pages for previous merged PRs (#2826, #2827) updated right away.

@darakian
Copy link
Contributor

darakian commented Nov 2, 2023

It was indeed :)
Not sure what was up. I had our system reprocess it and it looks like its gone through now.

@wtwhite
Copy link
Author

wtwhite commented Nov 2, 2023

Thanks @darakian, it's there for me now 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants