[Bug 1111233] New: VUL-0: CVE-2018-16737, CVE-2018-16738, CVE-2018-16758: tinc: Multiple issues fixed in the 1.0.35 release
http://bugzilla.opensuse.org/show_bug.cgi?id=1111233 Bug ID: 1111233 Summary: VUL-0: CVE-2018-16737, CVE-2018-16738, CVE-2018-16758: tinc: Multiple issues fixed in the 1.0.35 release Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/216345/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: michele.bologna@suse.com Reporter: jsegitz@suse.com QA Contact: security-team@suse.de Found By: Security Response Team Blocker: --- rh#1637481 CVE-2018-16758: Michael Yonli discovered that tinc 1.0.34 and earlier allow a man-in-the-middle attack that, even if the MITM cannot decrypt the traffic sent between the two endpoints, when the MITM can correctly predict when an ephemeral key exchange message is sent in a TCP connection between two nodes, allows the MITM to force one node to send UDP packets in plaintext. The tinc 1.1pre versions are not affected by this. CVE-2018-16738: Michael Yonli discovered that tinc versions 1.0.30 to 1.0.34 allow an oracle attack, similar to CVE-2018-16737, but due to the mitigations put in place for the Sweet32 attack in tinc 1.0.30, it now requires a timing attack that has only a limited time to complete. Tinc 1.1pre16 and earlier are also affected if there are nodes on the same VPN that still use the legacy protocol from tinc version 1.0.x. CVE-2018-16737: Michael Yonli discovered that tinc 1.0.29 and earlier allow an oracle attack that could allow a remote attacker to establish one-way communication with a tinc node, allowing it to send fake control messages and inject packets into the VPN. The attack takes only a few seconds to complete. Tinc 1.1pre14 and earlier allow the same attack if they are configured to allow connections from nodes using the legacy 1.0.x protocol. References: http://www.tinc-vpn.org/security/ https://bugzilla.redhat.com/show_bug.cgi?id=1637481 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-16737 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-16738 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-16758 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1111233 http://bugzilla.opensuse.org/show_bug.cgi?id=1111233#c1 Michele Bologna <michele.bologna@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |jsegitz@suse.com Flags| |needinfo?(jsegitz@suse.com) --- Comment #1 from Michele Bologna <michele.bologna@suse.com> --- Package has been updated to non-vulnerable tinc 1.0.35 on * OpenSUSE Leap 42.3 * OpenSUSE Leap 15.0 * OpenSUSE Factory Should we keep this bug open or can we close it? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1111233 http://bugzilla.opensuse.org/show_bug.cgi?id=1111233#c2 Johannes Segitz <jsegitz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jsegitz@suse.com) | --- Comment #2 from Johannes Segitz <jsegitz@suse.com> --- (In reply to Michele Bologna from comment #1) Thank you for the fix. Once security issues are resolved from you side you can reassign the bug to security@suse.de, we take it from there -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1111233 Johannes Segitz <jsegitz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|michele.bologna@suse.com |security-team@suse.de -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1111233 http://bugzilla.opensuse.org/show_bug.cgi?id=1111233#c3 Johannes Segitz <jsegitz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Johannes Segitz <jsegitz@suse.com> --- fix released -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com