[Free Module] Advanced Security Module

[MathiasReker 11]

PrestaShop Module: Security Lite

With this module the risk of getting hacked is decreased. You should always care about security. By using this module, you add another layer of security to your PrestaShop website, that will benefit you in case someone tries to get unauthorized access.

I did not add settings that are obviously already covered by PrestaShop core with another technique, but when that it said, if some technique having more layers is good practice, I added those extra layers of security.

 

Here are the features you will have with this FREE module:

• Brute force protection
• Ban IP’s
• Fix insecure permissions
• Disable right click
• Check system for vulnerabilities

 

Download it here (v. 2.0.0): securitylite.zip

Build to work with PrestaShop 1.7.0.0+

Documentation:

 

Thank you @zapalm for your suggestion.

This module use no overrides and passes PrestaShop's Validator.

 

 

I advise you to read the documentation, because some settings might need a little explanation. If you have any questions, do not hesitate to contact me. Let's be safe!

Edited May 12 by shinetech.dk
added new version of module.

[MathiasReker 11]

If you have suggestions for new features, please let me know in a comment. 😀

[zapalm 27]

Hello.

I have review your module a little and I have an advice for an improvement and a report for an issue.

1. Will be good, if you add to your free version of the module the functionality to check security vulnerabilities that are known from CVE. This is my free and open-source library, that you can use on your free and paid module versions both: Security vulnerability checker

2. In your SecurityLite::getContent() method there is an issue. Every loading of the module settings page, your module clear the system cache

    public function getContent()
    {
        $output = null;

        if ((bool) Tools::isSubmit('submitSecurityLiteModule')) { ... }

        return $output . $this->renderForm() . $this->checkSystem() . $this->securityPro() . $this->clearCache();
    }

    public function clearCache()
    {
        Tools::clearSmartyCache();
        Tools::clearXMLCache();
        Media::clearCache();
        Tools::generateIndex();
    }

 

Edited May 5 by zapalm
Fixed a typo

[TCHOUPI 233]

5 hours ago, zapalm said:

Hello.

I have review your module a little and I have an advice for an improvement and a report for an issue.

1. Will be good, if you add to your free version of the module the functionality to check security vulnerabilities that are known from CVE. This is my free and open-source library, that you can use on your free and paid module versions both: Security vulnerability checker

2. In your SecurityLite::getContent() method there is an issue. Every loading of the module settings page, your module clear the system cache

    public function getContent()
    {
        $output = null;

        if ((bool) Tools::isSubmit('submitSecurityLiteModule')) { ... }

        return $output . $this->renderForm() . $this->checkSystem() . $this->securityPro() . $this->clearCache();
    }

    public function clearCache()
    {
        Tools::clearSmartyCache();
        Tools::clearXMLCache();
        Media::clearCache();
        Tools::generateIndex();
    }

 

 

zapalm Your module error
 
[PrestaShop] Fatal error in module file :/home/.../../classes/module/Module.php(1361) : eval()'d code:
syntax error, unexpected 'zapalm' (T_STRING), expecting \\ (T_NS_SEPARATOR)

PS 1.6.1.23

Edited May 5 by TCHOUPI

[MathiasReker 11]

@zapalm Thank you.

1) I included your suggestions and made a fix for CVE-2018-7491.

2) You are right, it is superfluous to clear the case.

@TCHOUPI You can't install @zapalm's library as a module, it is a script. Btw. I included the checks in my module.
 

[TCHOUPI 233]

13 hours ago, shinetech.dk said:

@zapalm Thank you.

1) I included your suggestions and made a fix for CVE-2018-7491.

2) You are right, it is superfluous to clear the case.

@TCHOUPI You can't install @zapalm's library as a module, it is a script. Btw. I included the checks in my module.
 

ok thanks you, for ps 16 it can work ?
 

[MathiasReker 11]

The module works with 1.7+ only, sorry.

[zapalm 27]

14 hours ago, shinetech.dk said:

1) I included your suggestions and made a fix for CVE-2018-7491.

Advice for you for the future work  You lose the benefits if you copy the library's code into your module. The best way is using Composer to keep up to date the library and get new vulnerability checks

[MathiasReker 11]

22 minutes ago, zapalm said:

Advice for you for the future work  You lose the benefits if you copy the library's code into your module. The best way is using Composer to keep up to date the library and get new vulnerability checks

I had to refactor your functions. Also I don't want to include the checks for 1.6. :-)

[TCHOUPI 233]

2 hours ago, shinetech.dk said:

The module works with 1.7+ only, sorry.

ok Thanks you my friend

[mr_absinthe 2]

Hi, wanted to try the module, PS 1.7.5.1, debug enabled, see the image pls. What exactly does it mean?

[MathiasReker 11]

mr_absinthe, your server settings is not right configured.

You need to go to your php.ini file and look for allow_url_fopen. The value of this PHP configuration should be "On".

allow_url_fopen = On

Allow_url_fopen is required when you use PrestaShop.

If you don't know how, you can ask your hosting to change the value for you.

[mr_absinthe 2]

That is exactly what I have in php.ini. Cache cleared, browser and PS. Still the same.

[MathiasReker 11]

Can you try to restart your server? Do you have any files overriding your php.ini file?

[mr_absinthe 2]

Server rebooted. Still the same. No I don't have any overrides related to php.ini as far as I know. Resetting module didn't help either.

Edited May 6 by mr_absinthe

[MathiasReker 11]

10 minutes ago, mr_absinthe said:

Server rebooted. Still the same. No I don't have any overrides related to php.ini as far as I know. Resetting module didn't help either.

Weird.

I managed to reproduce the warning with "allow_url_fopen = Off". I made a refractory of my code to make it work with the setting off.

I will release new version tonight.

[mr_absinthe 2]

Weird is that I have

allow_url_fopen = On

[MathiasReker 11]

5 minutes ago, mr_absinthe said:

Weird is that I have

allow_url_fopen = On

Yes, it is weird that you get the warning with allow_url_fopen = On

But don't worry. I fixed it on my dev version. I will release a new version very soon.

Edited May 6 by shinetech.dk

[MathiasReker 11]

@mr_absinthe I just uploaded a new version, please give it a try. It should fix your warning. 🙂

[mr_absinthe 2]

Seems to be working fine, on my test server at the moment 😉 Will go for PRO version if there will be some kind of discount available in the near future. Is your "file changes" section checking for Size | Permissions {File | Group | Owner} | Time | Stamp ?

[MathiasReker 11]

44 minutes ago, mr_absinthe said:

Seems to be working fine, on my test server at the moment 😉 Will go for PRO version if there will be some kind of discount available in the near future. Is your "file changes" section checking for Size | Permissions {File | Group | Owner} | Time | Stamp ? 

The file changes will send you an e-mail with all files changes since last check. You decide how often you want to check. You set that interval in a cron-job. In the e-mail you will get a full path to the changed files. The file changes works by comparing a hash. 🙂

[MathiasReker 11]

There will be a discount period when next release of PRO version get released. I release a new version this week with new PRO features.

[mr_absinthe 2]

OK, if you will be sending a discount code, please let me have one as the current price is rather steep.

[MathiasReker 11]

On 5/7/2019 at 5:08 PM, mr_absinthe said:

OK, if you will be sending a discount code, please let me have one as the current price is rather steep.

i changed the price from 89 EURO to 59 EURO: https://addons.prestashop.com/en/website-security-access/44413-security-pro.html

[tapanda.gr 198]

What about the umask issue in core PrestaShop that converts new module directories to 0777 once they get uploaded?

[MathiasReker 11]

15 minutes ago, tapanda.gr said:

What about the umask issue in core PrestaShop that converts new module directories to 0777 once they get uploaded?

It is already solved. click on the tab "Permissions" then enable the features and "Save". This will run a script that fix all permissions on your PrestaShop website. Repeat this everytime you install a module.

 

It is overkill to hook this script or set it up as a cronjob. Lets keep the module lightweight so it does not affect your shops performance.

Edited May 23 by MathiasReker