Currently, the session cookie associated with a login on this issue tracker does
not have the secure flag set. This means that anyone controlling an upstream
router can potentially sniff the cookie (and thereby hijack the browser's
session) by tricking the user into sending a cleartext HTTP request to
bugs.g10code.com. This would be as simple as injecting a hidden "img" tag into
an unrelated cleartext HTTP request (e.g. a typical web search).