blacklist_calls¶
Blacklist various Python calls known to be dangerous¶
This blacklist data checks for a number of Python calls known to have possible security implications. The following blacklist tests are run against any function calls encoutered in the scanned code base, triggered by encoutering ast.Call nodes.
B301: pickle¶
Pickle library appears to be in use, possible security issue.
ID | Name | Calls | Severity |
---|---|---|---|
B301 | pickle |
|
Medium |
B302: marshal¶
Deserialization with the marshal module is possibly dangerous.
ID | Name | Calls | Severity |
---|---|---|---|
B302 | marshal |
|
Medium |
B303: md5¶
Use of insecure MD2, MD4, or MD5 hash function.
ID | Name | Calls | Severity |
---|---|---|---|
B303 | md5 |
|
Medium |
B304 - B305: ciphers and modes¶
Use of insecure cipher or cipher mode. Replace with a known secure cipher such as AES.
ID | Name | Calls | Severity |
---|---|---|---|
B304 | ciphers |
|
High |
B305 | cipher_modes |
|
Medium |
B306: mktemp_q¶
Use of insecure and deprecated function (mktemp).
ID | Name | Calls | Severity |
---|---|---|---|
B306 | mktemp_q |
|
Medium |
B307: eval¶
Use of possibly insecure function - consider using safer ast.literal_eval.
ID | Name | Calls | Severity |
---|---|---|---|
B307 | eval |
|
Medium |
B308: mark_safe¶
Use of mark_safe() may expose cross-site scripting vulnerabilities and should be reviewed.
ID | Name | Calls | Severity |
---|---|---|---|
B308 | mark_safe |
|
Medium |
B309: httpsconnection¶
Use of HTTPSConnection on older versions of Python prior to 2.7.9 and 3.4.3 do not provide security, see https://wiki.openstack.org/wiki/OSSN/OSSN-0033
ID | Name | Calls | Severity |
---|---|---|---|
B309 | httpsconnection |
|
Medium |
B310: urllib_urlopen¶
Audit url open for permitted schemes. Allowing use of ‘file:” or custom schemes is often unexpected.
ID | Name | Calls | Severity |
---|---|---|---|
B310 | urllib_urlopen |
|
Medium |
B311: random¶
Standard pseudo-random generators are not suitable for security/cryptographic purposes.
ID | Name | Calls | Severity |
---|---|---|---|
B311 | random |
|
Low |
B312: telnetlib¶
Telnet-related functions are being called. Telnet is considered insecure. Use SSH or some other encrypted protocol.
ID | Name | Calls | Severity |
---|---|---|---|
B312 | telnetlib |
|
High |
B313 - B320: XML¶
Most of this is based off of Christian Heimes’ work on defusedxml: https://pypi.python.org/pypi/defusedxml/#defusedxml-sax
Using various XLM methods to parse untrusted XML data is known to be vulnerable to XML attacks. Methods should be replaced with their defusedxml equivalents.
ID | Name | Calls | Severity |
---|---|---|---|
B313 | xml_bad_cElementTree |
|
Medium |
B314 | xml_bad_ElementTree |
|
Medium |
B315 | xml_bad_expatreader |
|
Medium |
B316 | xml_bad_expatbuilder |
|
Medium |
B317 | xml_bad_sax |
|
Medium |
B318 | xml_bad_minidom |
|
Medium |
B319 | xml_bad_pulldom |
|
Medium |
B320 | xml_bad_etree |
|
Medium |
B321: ftplib¶
FTP-related functions are being called. FTP is considered insecure. Use SSH/SFTP/SCP or some other encrypted protocol.
ID | Name | Calls | Severity |
---|---|---|---|
B321 | ftplib |
|
High |
B322: input¶
The input method in Python 2 will read from standard input, evaluate and run the resulting string as python source code. This is similar, though in many ways worse, then using eval. On Python 2, use raw_input instead, input is safe in Python 3.
ID | Name | Calls | Severity |
---|---|---|---|
B322 | input |
|
High |
B323: unverified_context¶
By default, Python will create a secure, verified ssl context for use in such classes as HTTPSConnection. However, it still allows using an insecure context via the _create_unverified_context that reverts to the previous behavior that does not validate certificates or perform hostname checks.
ID | Name | Calls | Severity |
---|---|---|---|
B322 | unverified_context |
|
Medium |