-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Jetty 9.4.51: org.eclipse.jetty.http.HttpCookie.getSetCookie
does not handle RFC6265_LEGACY
#9717
Comments
This is a result of the PR: #9352 . Which is similar to the change for Jetty 10, but there the Compare https://github.com/eclipse/jetty.project/blob/7f55e82d005436516efd136e2b8362cb64c8411e/jetty-http/src/main/java/org/eclipse/jetty/http/HttpCookie.java#L282 with https://github.com/eclipse/jetty.project/blob/986751c1e1b10814feba9e88eef4870ad9910407/jetty-http/src/main/java/org/eclipse/jetty/http/HttpCookie.java#L286 to see the issue. |
org.eclipse.jetty.http.HttpCookie.getSetCookie
does not handle RFC6265_LEGACY
org.eclipse.jetty.http.HttpCookie.getSetCookie
does not handle RFC6265_LEGACY
I have an additional question: does using RFC6265_LEGACY mean you are still exposed to https://nvd.nist.gov/vuln/detail/CVE-2023-26049 ? |
Keep in mind that Jetty 9.x is now at End of Community Support, you should be on Jetty 10, or Jetty 11, or even Jetty 12 by now. See: We have testcases in 9.4.51 for Also CVE-2023-26049 is for a cookie parsing vulnerability. Using RFC6265_LEGACY will expose you to that vulnerability. |
Closing, not a Bug, and is also for an End of Community Support release. |
Jetty version(s)
9.4.51
Description
org.eclipse.jetty.http.HttpCookie.getSetCookie
does not handleRFC6265_LEGACY
and will result inIllegalStateException
.How to reproduce?
Set
and add a cookie.
The text was updated successfully, but these errors were encountered: