12th August 2016
|
|
More noise than signal
|
|
Join Date: May 2008
Location: USA
Posts: 7,977
|
|
- The best place to ask questions of the Project would be through their mailing lists. This is a third party forum, and we're primarily users here, not experts. I may try to help answer questions, but I'm in the former category, not the latter.
- The vulnerability you cite references only the Linux kernel. The specific Linux kernel source code module referenced is net/ipv4/tcp_input.c, which is both Linux-specific and has a completely different provenance from the OpenBSD protocol stack's module with a similar name: src/sys/netinet/tcp_input.c. If you look at the two modules, you can see that they are completely different.
- The only way to know for certain if there is a similar vulnerability would be to test the exploit.
I don't have the skills to develop exploit tests myself. I attempted to do so recently for a pair of CVEs affecting one of the ports I maintain, in order to show the upstream project that they were vulnerable and should apply patches. I was unsuccessful in recreating the exploit tests but the upstream project applied the patches anyway. The CVE patches are in the current version of the port; the updated port removes the CVE patches as they are now included in the application. http://marc.info/?l=openbsd-ports&m=146997546125497&w=2
Last edited by jggimi; 12th August 2016 at 11:09 AM.
Reason: Added additional info regarding the port, plus a link
|