Bug #3695
closed
We're already aware and investigating.
As far as we can tell it may not be critical for most. As with Heartbleed it primarily would affect OpenVPN in SSL/TLS mode and only then if you chose NOT to use a TLS auth key on the VPN. Harder still, someone apparently has to be in a position to intercept both client and server traffic to be able to inject the questionable packets into the connection stream to cause harm. It doesn't leak data like Heartbleed, but may allow someone to decrypt traffic flowing through the VPN.
It may also impact the GUI but as always if people followed our recommendations and keep GUI access restricted then it wouldn't be an issue there either.
- Target version set to 2.1.4
- Status changed from New to Resolved
was fixed in 2.1.4, ticket never got closed out.
Also available in: Atom
PDF