-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
blog: clarify in async hook DoS post and add CWE pointers #8556
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
It seems there are still some confusions from how this weakness works, especially since APM tools are only part of the reproduction but are not vulnerable per-se. This patch tries to clarify a bit and add some pointers to the CWEs that apply.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
👋 Codeowner Review RequestThe following codeowners have been identified for the changed files: Team reviewers: @nodejs/nodejs-website Please review the changes when you have a chance. Thank you! 🙏 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This pull request clarifies the async hooks DoS vulnerability blog post to address confusion about the nature of the weakness. The changes emphasize that APM tools are not vulnerable themselves but enable reproduction of an edge case that exposes a broader ecosystem weakness: reliance on unspecified stack overflow behavior.
Changes:
- Clarified that the issue is an edge case affecting recovery from stack exhaustion when async_hooks are enabled
- Added CWE references (CWE-758 and CWE-674) to document the underlying weaknesses
- Updated section titles to better reflect the nature of the issue ("The Reproduction" instead of "The Bug", APM tools "Makes It Easier to Reproduce" rather than implying they are affected)
- Improved language throughout to distinguish between the mitigation and the underlying ecosystem weakness
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Outdated
Show resolved
Hide resolved
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8556 +/- ##
==========================================
+ Coverage 74.96% 74.97% +0.01%
==========================================
Files 103 103
Lines 9036 9036
Branches 312 312
==========================================
+ Hits 6774 6775 +1
+ Misses 2260 2259 -1
Partials 2 2 ☔ View full report in Codecov by Sentry. |
…ion-async-hooks.md Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
…ion-async-hooks.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Joyee Cheung <joyeec9h3@gmail.com>
mcollina
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
apps/site/pages/en/blog/vulnerability/january-2026-dos-mitigation-async-hooks.md
Show resolved
Hide resolved
|
Added a callout to the proper tail calls in the reproduction to help understanding it; also I noticed the list isn't working without the |
It seems there are still some confusions from how this weakness works, especially since APM tools are only part of the reproduction but are not vulnerable per-se. This patch tries to clarify a bit and add some pointers to the CWEs that apply.
Description
Validation
Related Issues
Check List
pnpm formatto ensure the code follows the style guide.pnpm testto check if all tests are passing.pnpm buildto check if the website builds without errors.