[GHSA-x9vc-6hfv-hg8c] Npgsql vulnerable to SQL Injection via Protocol Message Size Overflow

[NinoFloris]

Updates

• Affected products
• Description
• References

Comments
I'm a maintainer for Npgsql. It was unclear to us the security vulnerability author provided the template for the advisory, and that we had to edit it. The suggested changes trim down the summary, remove the POCs links and provide the correct affected and patched versions.

[github]

Hi there @paul-gerste-sonarsource and @NinoFloris! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.

This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

[NinoFloris]

@advisory-database could you please take a look? Users are opening quite some issues and PRs (7 so far over here) related to this. Our apologies for the mistake, we were unfamiliar with the GitHub process.

[advisory-database]

Hi @NinoFloris! 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!

[Kritner]

any idea how long the change needs to be in place before it'll stop being flagged as a NU1903? I would have thought it'd get checked "each time" but maybe there's some level of caching involved. (I realize the answer is probably not known from this repo's maintainers but...)