GitHub - v-p-b/DangerousPHPFunctions: Growing list of potentially dangerous PHP functions

This repository has been archived by the owner on Jun 24, 2019. It is now read-only.

v-p-b / DangerousPHPFunctions Public archive

Notifications You must be signed in to change notification settings
Fork 11
Star 52

Growing list of potentially dangerous PHP functions

52 stars 11 forks Branches Tags Activity

Notifications

Name		Name	Last commit message	Last commit date
Latest commit History 19 Commits
README		README
dangerous_strings.rb		dangerous_strings.rb
footer.html		footer.html
generate_html.php		generate_html.php
generate_ini.sh		generate_ini.sh
header.html		header.html
likely_used.txt		likely_used.txt
php_dangerous.txt		php_dangerous.txt

Repository files navigation

WARNING
=======

!!! THIS REPO IS HIGHLY OUTDATED, YOU PROBABLY SHOULDN'T USE IT !!! 

README
======

This is a list of potentially dangerous PHP functions which should be disabled in most of the PHP web hosting environments.

The php_dangerous.txt file contains the categorized list of these functions. 
The likely_used.txt file contains functions which can be used dangerously but are required by many applications.

Format: 

    [Category name ]
    function_name # comment

The generate_ini.sh script generates a php.ini entry from the list. Usage:

generate_ini.sh php_dangerous.txt

DISCLAIMER
==========

Use at your own risk! Hardening should always be done in accordance with the current environment.