Closed Bug 549092 Opened 16 years ago Closed 15 years ago

Update Pound on https://*.momo.com/, due to TLS bug

Categories

(Mozilla Messaging Graveyard :: Server Operations, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: BenB, Assigned: gozer)

Details

Shredder, when contacting the ISP DB, says on the error console: live.mozillamessaging.com : potentially vulnerable to CVE-2009-3555 See <http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2009-3555>. Maybe update Apache. (There's a fix available since some time.)
Yeah, that's just because we still allow ssl renegociation. Unfortunately, at the moment, we are not using Apache for SSL termination, so I am still waiting for a patch to Pound to patch that hole.
Group: mozilla-messaging-confidential
gozer, as reporter and per Mozilla security policy, I ask to remove the confidentially flag. This bug publicly visible anyways, anybody can see what I saw in Shredder's error console.
(In reply to comment #2) > gozer, as reporter and per Mozilla security policy Apologies, I am not entirely familiar with the security policies (url to it?) and have removed the flag.
Group: mozilla-messaging-confidential
Contacted vendor <http://www.apsis.ch/pound/index_html> (Mozilla security policy: <http://www.mozilla.org/projects/security/security-bugs-policy.html>. Thanks for removing the flag! You couldn't know that I intentionally didn't set any security flags.)
Summary: Update Apache on live.momo, due to TLS bug → Update Pound on https://*.momo.com/, due to TLS bug
Pound vendor/author responded. He says that no patch is necessary. openssl 0.9.8l and later implements the fix. So, false alarm (Firefox bug 549641). See also <https://www.ssllabs.com/ssldb/analyze.html?d=live.mozillamessaging.com> for tests. Leaving it to gozer to verify.
No, OpenSSL 0.9.8m support RFC 5746, the best you can do with 'l' is disable renegotiation. but that's a configuration option -- have you actually done that?
(In reply to comment #6) > No, OpenSSL 0.9.8m support RFC 5746, the best you can do with 'l' is disable > renegotiation. but that's a configuration option -- have you actually done > that? Nope, AFAIK, Pound doesn't have that option yet. So, even if I rebuild it against OpenSSL 0.9.8l, I can't fix it yet.
Can you build against 0.9.8m?
(note: he said "or later")
(In reply to comment #8) > Can you build against 0.9.8m? I certainly can, but it's non-trivial, as I am using the stock Pound from CentOS. I'd rather see a Pound fix that allows me to disable SSL renegociation in Pound itself. In any case, our risk exposure to this bug is somewhat near-zero. My understanding is the only risk is that someone could inject some stuff in a client request to our sites. For instance, a MITM could trick, maybe, you from getting the autoconfig XML for gmail.com when your domain is msn.com. Since what we run on momo.com is almost entirely static stuff, there is very little practical risk on our end. BenB, any chance to ask the Pound folks for a DisableSSLRenegociation option ?
> any chance to ask the Pound folks for a DisableSSLRenegociation option ? He said "any further questions to the mailing list", so I guess he wasn't thrilled about the direct mail :). As dveditz said in bug 549641, disabling renegotiation would avoid the bug entirely, but not suppress the error message. So, I guess you need openssl 0.9.8m in any case. Is Pound statically linked against openssl? If not, would it suffice to just install (and possibly compile) a new openssl?
(In reply to comment #10) > > Can you build against 0.9.8m? > > I certainly can, but it's non-trivial, as I am using the stock Pound from > CentOS. I'd rather see a Pound fix that allows me to disable SSL renegociation > in Pound itself. If you build against openSSL 0.9.8m or later then it doesn't matter whether you disable renegotiation or not, it will handle renegotiation securely.
Resolved when we upgraded the webheads to Centos 5.5
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.