You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dependabot alerts#99
cookie accepts cookie name, path, and domain with out of bounds characters #99
Open Opened 2 months ago on cookie (npm) · package-lock.json
Dependabot cannot update cookie to a non-vulnerable version
The latest possible version that can be installed is 0.6.0 because of the following conflicting dependencies:
Package
Affected versions
Patched version
cookie
(npm)
< 0.7.0
0.7.0
Impact
The cookie name could be used to set other fields of the cookie, resulting in an unexpected cookie value. For example, serialize("userName=<script>alert('XSS3')</script>; Max-Age=2592000; a", value) would result in "userName=<script>alert('XSS3')</script>; Max-Age=2592000; a=test", setting userName cookie to <script> and ignoring value.
A similar escape can be used for path and domain, which could be abused to alter other fields of the cookie.
Patches
Upgrade to 0.7.0, which updates the validation for name, path, and domain.
Workarounds
Avoid passing untrusted or arbitrary values for these fields, ensure they are set by the application instead of user input.
Dependabot alerts #99
cookie accepts cookie name, path, and domain with out of bounds characters #99
Open Opened 2 months ago on cookie (npm) · package-lock.json
Dependabot cannot update cookie to a non-vulnerable version
The latest possible version that can be installed is 0.6.0 because of the following conflicting dependencies:
[email protected] requires [email protected] via a transitive dependency on [email protected]
No patched version available for cookie
The earliest fixed version is 0.7.0.
Package
Affected versions
Patched version
cookie
(npm)
< 0.7.0
0.7.0
Impact
The cookie name could be used to set other fields of the cookie, resulting in an unexpected cookie value. For example, serialize("userName=<script>alert('XSS3')</script>; Max-Age=2592000; a", value) would result in "userName=<script>alert('XSS3')</script>; Max-Age=2592000; a=test", setting userName cookie to <script> and ignoring value.
A similar escape can be used for path and domain, which could be abused to alter other fields of the cookie.
Patches
Upgrade to 0.7.0, which updates the validation for name, path, and domain.
Workarounds
Avoid passing untrusted or arbitrary values for these fields, ensure they are set by the application instead of user input.
References
jshttp/cookie#167
The text was updated successfully, but these errors were encountered: