Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: This is still a WIP page but be sure to read at least the Warning

This is still a WIP page but be sure to read at least the Warning

Info
titleWhat is this page about?

This page is about security as in "external security". In other words it's not about authentication or authorisation, for that refer to OFBiz Security Permissions.

But about about keeping your OFBis instance secure from external exploits, and prevent vulnerabilities as soon as they are known.

...

You can trust the Apache OFBiz PMC Members and Committers, we do our best to keep OFBiz secure. But despite our best efforts we migth sometimes overlook a security issue. In such cases, as explained at https://ofbiz.apache.org/download.html, we strongly encourage OfBiz users to report security problems affecting OFBiz to the private security mailing list of the ASF Security Team, before disclosing them in a public forum. Please see the page of the ASF Security Team for further information and contact information. Also in case of doubt, refer to the current page where quick fixes not already released might be explained.

Sometimes the OFBIz code itself is not the culprit. OFBiz relies on many Java librairies, and if one of them has a flaw we can't always wait it's fixed to warn and protect our users. This is for instance what happened with the infamous 2015 Java unserialize vulnerability. OFBiz was concerned affected by 2 librairires: Commons Collections

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyOFBIZ-6726
and Groovy
Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyOFBIZ-6568
. As you can see at OFBIZ-6736, we waited the Commons Collections update to fix the issue, because it was not much disclosed then. But with the article above the buzz began to spread and we could not wait to be able to update Groovy. So a temporary workaround was adopted as explained in OFBIZ-6568.

 

Warning
titleBe safe!

Until we update the Groovy librairy, we recommend you to have a look at http://svn.apache.org/viewvc?view=revision&revision=1717058 and so to use the start-secure ant target rather than the start one, or any other possibilities offered by OFBIZ-6568 (startofbiz.sh/bat, etc). Also to have an historical view on the OFBiz security you can refer to

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyOFBIZ-1525

 

Roughly I (Jacques Le Roux) personaly believe there are 3 categories of OFBiz users:

  1. Those who use OFBiz only in an internal manner, without any connections with the Internet, most of the time only the OFBiz backend is then used. They should be the less concerned.
    But this category tends to be less and less represented. Nowaydays most of the organisations need somehow to be connected.
  2. Users working in a secured environment, notably through firewalls and proxies. They should less fear security vulnerabilities. But you can't never be sure, black hackers are always trying...
  3. Users working in a less secure environment. For instance using the Out Of The Box (OOTB) OFBiz ecommerce/ecomseo solutions with a direct access from the Internet to it.

 Now you might wonder how to keep your own OFBiz instance safe from vulnerabilites and maybe how to contribute your exeperience with other OFBiz users.

Step-by-step guide

...

In any cases, always check that your version is up to date, see the "Security Vulnerabilities" section at https://ofbiz.apache.org/download.html. If you use the trunk be sure to closely follow JIRA issues and revisions commits regarding security and check OFBIZ-1525. Then apply patches as soon as possible.

...

 

Now you might wonder how to yourself keep your own OFBiz instance safe from vulnerabilities and maybe how to contribute your experience to other OFBiz users. Having worked on the OFBiz security for few years, these are the tools I (Jacques Le Roux) personnaly recommend. For each I will explain in specific pages how to share your results.

  • For Java: OWASP Dependency Check Since it reports a lot of false positive or not really needing our attention I will create a page to explain how to use it and share results.
  • For JavaScript: Retire.js
  • For HTML headers: https://cyh.herokuapp.com/cyh. Those are less important but I will try to clear the situation soon!

There are other web oriented, tools like OWASP Zed Attack, Beef or IBM Security AppScan. But most of the time they are too general, and totally parsing OFBiz can take a lot of time or be quite a challenge if done manually. You can find more penetration tools here

...