The request when piped through Burp Suite's proxy, has the following response headers:
For more information about why this attribute is so important, refer to this article
Tested on ZNC 1.7.5
The initial cookie given to the user when navigating to the ZNC home page lacks the `HttpOnly` attribute.
Strangely, the code that I believe is supposed to set this attribute looks like it should be working: https://github.com/znc/znc/blob/0ab205ccfa278eaa94063b4ad5e30d997e4c8311/src/HTTPSock.cpp#L745
The request when piped through Burp Suite's proxy, has the following response headers:

For more information about why this attribute is so important, refer to [this article](https://blog.codinghorror.com/protecting-your-cookies-httponly/)
* Tested on ZNC 1.7.5
<!-- github-sync-id:516443094 -->
Burp suite doesn't change responses. It only acts as a proxy server to watch traffic and re-send requests if desired.
I should also mention that this issue was first flagged by OpenVAS, so it's not an isolated incident.
> Looks like Burp Suite is messing with the cookie.
Burp suite doesn't change responses. It only acts as a proxy server to watch traffic and re-send requests if desired.
I should also mention that this issue was first flagged by OpenVAS, so it's not an isolated incident.
<!-- github-comment-id:549049702 -->
Tried that same request in Postman and the Set-Cookie header does have HttpOnly now. Strange.
Can't reproduce the problem so I'll close this issue.
Tried that same request in Postman and the Set-Cookie header does have HttpOnly now. Strange.
Can't reproduce the problem so I'll close this issue.
<!-- github-comment-id:549614568 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The initial cookie given to the user when navigating to the ZNC home page lacks the
HttpOnlyattribute.Strangely, the code that I believe is supposed to set this attribute looks like it should be working: https://github.com/znc/znc/blob/0ab205ccfa278eaa94063b4ad5e30d997e4c8311/src/HTTPSock.cpp#L745
The request when piped through Burp Suite's proxy, has the following response headers:
For more information about why this attribute is so important, refer to this article
Looks like Burp Suite is messing with the cookie.
Burp suite doesn't change responses. It only acts as a proxy server to watch traffic and re-send requests if desired.
I should also mention that this issue was first flagged by OpenVAS, so it's not an isolated incident.
Try without Burp. Does it still miss HttpOnly?
Tried that same request in Postman and the Set-Cookie header does have HttpOnly now. Strange.
Can't reproduce the problem so I'll close this issue.