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.

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

Security concern: qs vulnerable to Prototype Pollution #436

Closed
2 tasks done
pavikrishna opened this issue Feb 21, 2024 · 0 comments · Fixed by #438
Closed
2 tasks done

Security concern: qs vulnerable to Prototype Pollution #436

pavikrishna opened this issue Feb 21, 2024 · 0 comments · Fixed by #438
Labels
bug Something isn't working

Comments

@pavikrishna
Copy link

Duplicates

  • I have searched the existing issues

Latest version

  • I have tested the latest version

Current behavior 😯

qs before 6.10.3 allows attackers to cause a Node process hang because an __ proto__ key can be used. In many typical web framework use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[proto]=b&a[proto]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4.

Expected behavior 🤔

can you upgrade your qs version to a non affected version
Package: qs (npm)
Affected versions: >= 6.10.0, < 6.10.3
Patched version : 6.10.3

Steps to reproduce 🕹

Steps:

Screenshots or Videos 📹

No response

Platform 🌍

all of the above
@giphy/js-fetch-api@npm:5.3.0

GIPHY-JS SDK version

latest version and above, @giphy/js-fetch-api@npm:5.3.0

TypeScript version

No response

Additional context 🔦

No response

@pavikrishna pavikrishna added the bug Something isn't working label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant