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

Skip to content

doc: add constraints for mem leak to threat model #58917

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Jul 24, 2025
+15 −0
Merged

doc: add constraints for mem leak to threat model #58917

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
666abb3
doc: add constraints for mem leak to threat model
RafaelGSS Jul 1, 2025
b3b9bbc
fixup! doc: add constraints for mem leak to threat model
RafaelGSS Jul 7, 2025
6da6f83
fixup! fixup! doc: add constraints for mem leak to threat model
RafaelGSS Jul 17, 2025
30a830c
fixup! fixup! fixup! doc: add constraints for mem leak to threat model
RafaelGSS Jul 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
doc: add constraints for mem leak to threat model 
As discussed in nodejs-private/node-private#719.

We should clarify what the criteria are to accept
memory leak as a vulnerability (potential DoS).

Signed-off-by: RafaelGSS <[email protected]>
  • Loading branch information
@RafaelGSS
RafaelGSS committed Jul 1, 2025
commit 666abb33bf1be11d05c084dd0b42dc3fc1d99105
5 changes: 5 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,11 @@ does not trust is considered a vulnerability:
the correct use of Node.js APIs.
* The unavailability of the runtime, including the unbounded degradation of its
performance.
* Memory leaks qualify as vulnerabilities when all of the following criteria are met:
* The API is being correctly used
* The API doesn't have a warning against its usage in a production environment
* The API is on stable (2.0) status
* The memory leak is significant, causing a DoS fast or in a user-uncontrolled space (for instance, on HTTP parsing)

If Node.js loads configuration files or runs code by default (without a
specific request from the user), and this is not documented, it is considered a
Expand Down
Loading