Access to add and change pages is restricted. See: https://cwiki.apache.org/confluence/display/OFBIZ/Wiki+access

Skip to end of metadata
Go to start of metadata

What is this page about?

This page is about security as in "external security". In other words it's not about authentication nor authorisation, for that refer to OFBiz Security Permissions.
But about keeping your OFBiz instance secure from external exploits, and prevent vulnerabilities as soon as they are known.

Content

You can trust the Apache OFBiz PMC Members and Committers do their best to keep OFBiz secure. But despite our best efforts we might 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 OFBiz project (security AT ofbiz.apache.org), before disclosing them in a public forum. Please see the page of the ASF Security Team for further information and contact details. Also in case of doubt, refer to the current page where quick fixes not already released might be explained.

Also you should update your release version as soon as a security update is mentioned at https://ofbiz.apache.org/download.html#vulnerabilities.
If you are using a release branch rather than a released package, as soon as the release branch contains the security update, you should update ("svn up") your working copy, test and apply in production...

You might refer to OFBIZ-1525 - Issue to group security concerns Open for details on security.

 

Be safe!

Be sure to read The infamous Java serialization vulnerability page if, within your OFBiz instance, you use/add RMI, JMX, Spring, or/and any external librairies not included in OFBiz out of the box.

Who is concerned?

Roughly 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. Nowadays 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.

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 security patches as soon as possible, and of course check this page! (wink)

How to check yourself, and possibly share and help

Now you might wonder how to keep your own OFBiz instance safe from vulnerabilities and maybe 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) personaly recommend. For each it's explained in specific pages how they work  and how to share your results

Java

Currently we have no known Java vulnerabilities in OFBiz code. There are some vulnerable third parties libraries. Fortunately it's not high vulnerabilities. You can know more by looking at the last report file. We use the OWASP Dependency Check to check third parties libraries OFBiz uses.This page explains how to use it and to share results: About OWASP Dependency Check

JavaScript

For JavaScript: Retire.js see this page: About retire.js

HTTP headers

For HTTP headers: https://cyh.herokuapp.com/cyh.This page gives more information: How to Secure HTTP Headers

Penetration tools

There are 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.

In December 2015, I ran a complete (100%) OWASP Zed Attack automated (Quick Start) penetration session against a locale instance of OFBiz backend (trunk head) running on localhost. It started with the same link used for backend demos. No major flaws were discovered.