Skip to content

x/vulndb: suggestion regarding GO-2025-3408 #3453

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

Closed
finnigja opened this issue Feb 5, 2025 · 2 comments
Closed

x/vulndb: suggestion regarding GO-2025-3408 #3453

finnigja opened this issue Feb 5, 2025 · 2 comments

Comments

@finnigja
Copy link

finnigja commented Feb 5, 2025

Report ID

GO-2025-3408

Suggestion/Comment

👋 from HashiCorp Security. This report, GO-2025-3408, was proposed for and published in vulndb before we had a chance to review / investigate fully.

Based on investigations documented & concluded elsewhere (ref hashicorp/yamux#142 & hashicorp/yamux#143), we do not believe that Yamux is exposed to a denial of service vulnerability as described.

Yamux requires that dependent applications explicitly close streams on write errors. Coding errors may cause network connectivity issues, but Yamux does not attempt to defend against these errors by design.

This library has a broad set of dependents and - in order to avoid confusion and / or vulnerability scanner driven churn for those dependents - we request that this entry be removed from the database or otherwise marked as invalid. Thanks!

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/647035 mentions this issue: data/reports: withdraw GO-2025-3408

@tatianab
Copy link
Contributor

tatianab commented Feb 6, 2025

Thanks for letting us know. I have withdrawn the report.

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

No branches or pull requests

3 participants