mirror of
https://github.com/linuxkit/linuxkit.git
synced 2025-07-20 01:29:07 +00:00
Merge pull request #1946 from tych0/2017-05-30-cves
docs: add some writeups of recent CVEs
This commit is contained in:
commit
b5b0c08400
@ -5,6 +5,11 @@ The incomplete list below is an assessment of some CVEs, and LinuxKit's resilien
|
||||
|
||||
### Bugs mitigated:
|
||||
|
||||
* [CVE-2017-9075](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9075):
|
||||
Requires CONFIG_IP_SCTP=y, which we do not set.
|
||||
* [CVE-2017-9076](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9076):
|
||||
Requires CONFIG_IP_DCCP=y, which we do not set. (However, we are vulnerable
|
||||
to the ipv6 pieces that this patch fixes.)
|
||||
* [CVE-2017-1000363](http://www.openwall.com/lists/oss-security/2017/05/23/16):
|
||||
This CVE requires `CONFIG_PRINTER=y`, so we are not vulnerable.
|
||||
* [CVE-2017-2636](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2636)
|
||||
@ -16,3 +21,18 @@ The incomplete list below is an assessment of some CVEs, and LinuxKit's resilien
|
||||
(specifically, kernels `=> 4.9, >= 4.4.21`, LinuxKit mitigates this bug.
|
||||
|
||||
### Bugs not mitigated:
|
||||
|
||||
|
||||
### Bugs outstanding:
|
||||
|
||||
* [CVE-2017-8890](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8890)
|
||||
All users can do `accept()`, so we are vulnerable.
|
||||
* [CVE-2017-9077](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9077)
|
||||
Same as CVE-2017-8890, but for ipv6.
|
||||
* [CVE-2017-9074](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9074):
|
||||
Users have access to ipv6 sockets, so we are vulnerable.
|
||||
* [CVE-2017-9242](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9242):
|
||||
Same as CVE-2017-9074.
|
||||
* [CVE-2017-9076](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9076):
|
||||
Users have access to ipv6 sockets (note that part of this is mitigated as
|
||||
well, so listed above: we do not set CONFIG_IP_DCCP).
|
||||
|
Loading…
Reference in New Issue
Block a user