Skip to content
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

Update timing_attack_node.yaml #113

Merged
merged 1 commit into from
Mar 13, 2024
Merged

Update timing_attack_node.yaml #113

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 2 additions & 1 deletion njsscan/rules/semantic_grep/crypto/timing_attack_node.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -485,7 +485,8 @@ rules:
return api != $X;
message: >-
String comparisons using '===', '!==', '!=' and '==' is vulnerable to timing attacks.
More info: https://snyk.io/blog/node-js-timing-attack-ccc-ctf/
A timing attack allows the attacker to learn potentially sensitive information by, for example, measuring how long it takes for the application to respond to a request.
More info: https://nodejs.org/en/learn/getting-started/security-best-practices#information-exposure-through-timing-attacks-cwe-208
languages:
- javascript
severity: WARNING
Expand Down
Loading