This was fixed in version 2.2.1
.
If you are unable to update, ensure that user supplied data isn't able to flow to HTTP headers. If it does, pre-sanitize for CRLF characters.
I've been poking at libraries to see if they are vulnerable to HTTP Response Splitting and Jooby is my third case of finding this vulnerability.
This roots cause back to this line in the Jooby codebase:
https://github.com/jooby-project/jooby/blob/93cfc80aa20c188f71a442ea7a1827da380e1c27/modules/jooby-netty/src/main/java/io/jooby/internal/netty/NettyContext.java#L102
The DefaultHttpHeaders
takes a parameter validate
which, when true
(as it is for the no-arg constructor) validates that the header isn't being abused to do HTTP Response Splitting.
This vulnerability was reported by @JLLeitschuh (Twitter)
If you have any questions or comments about this advisory: * Open an issue in jooby-project/jooby
{ "nvd_published_at": "2020-04-06T15:15:00Z", "github_reviewed_at": "2020-04-02T23:59:56Z", "severity": "CRITICAL", "github_reviewed": true, "cwe_ids": [ "CWE-444" ] }