Critical: Highly critical
Impact: System access
Where: From remote
Solution Status: Unpatched

Software: bigAPE-Backup 1.x (component for Mambo)

Select a product and view a complete list of all Patched/Unpatched Secunia advisories affecting it.

Description:
mdx has discovered a vulnerability within bigAPE-Backup, which can be exploited by malicious people to compromise a vulnerable system.

Input passed to the "mosConfig_absolute_path" parameter in components/com_babackup/classes/Tar.php is not properly verified before being used to include files. This can be exploited to include arbitrary files from local or external resources.

The vulnerability has been confirmed in version 1.1. Other versions may also be affected.

Solution:
Edit the source code to ensure that input is properly verified.

Read more: http://secunia.com/advisories/21574/

smart wrote:
Solution:
Edit the source code to ensure that input is properly verified.

Hi does anybody know what code parts need to be edited ?

This usage of mosConfig_absolute_path could be prevented by adding :

Code: Select all

/** ensure this file is being included by a parent file */
defined( '_VALID_MOS' ) or die( 'Direct Access to this location is not allowed.' );

at the very top of each file. There are several of them not having this, and they should!

Confirmation from core or experienced developer is needed here though!

[EDIT] after checking more, only Tar.php needs this fix. Other files missing it do not require as they are only libraries and do not have directly executable code in them

I have patched and attached the Tar.php file, it was obtained from a PHP resource (thought it was PEAR, but might be wrong). I'm not currently ready to release a new version of the bigAPE Backup as we are working on a v1.6 which will be released in the near future

Hope this resolves the issue

Thanks bigAPE for a very usefull component. I unistalled this and others on the security risk list. Hopefully bigAPE-Backup gets the "Fixed" flag flying soon on the list- I'm ready to get away from my cPanel backups and re-install your patched component.

cmyksteve wrote:Thanks bigAPE for a very usefull component. I unistalled this and others on the security risk list. Hopefully bigAPE-Backup gets the "Fixed" flag flying soon on the list- I'm ready to get away from my cPanel backups and re-install your patched component.

Your very welcome. We are only sorry that our commercial projects have kept us away from our GPL CMS Components. We do have a new version almost ready to go. It includes much better Database Backup code and the ability to migrate content articles between Mambo/Joomla sites. It needs a further round of testing and updated documentation, but I feel we are close to releasing it for Beta.

Could someone from the Security Team please give us the thumbs up or down on the patch bigAPE has supplied for his backup component. As of 9.24.06, it's still number 6 on the RobS hit list 
http://forum.joomla.org/index.php/topic,79477.0.html.

bigAPE wrote:

cmyksteve wrote:Thanks bigAPE for a very usefull component. I unistalled this and others on the security risk list. Hopefully bigAPE-Backup gets the "Fixed" flag flying soon on the list- I'm ready to get away from my cPanel backups and re-install your patched component.

Your very welcome. We are only sorry that our commercial projects have kept us away from our GPL CMS Components. We do have a new version almost ready to go. It includes much better Database Backup code and the ability to migrate content articles between Mambo/Joomla sites. It needs a further round of testing and updated documentation, but I feel we are close to releasing it for Beta.

Can you give us some kind of timeline (not that we will keep you at this timeline - but only for the idea).

Has anybody re-installed the bigAPE backup component since the security patch was released? Any security issues with it?

Has anyone from the security team taken a look at the patch that bigAPE provided in this thread a few messages back?
I see a new vulnerability list has been posted in the forum and the bigAPE backup compenent is still listed but my guess is that his patch has been overlooked. I've gotten no replies from the PMs sent to smart or RobS concerning this component.

Be sure to not leave generated archives (backups) on the server, read more here: http://dev.joomla.org/component/option, ... ,33/p,198/

I have also PM Robs on this several weeks ago, with no response. Just wondering whether they think the patch is not enough!

[EDIT] I have just PMed Ron Liskey about this

The vulnerabilities list is updated with a link back to this topic.

Thanks rliskey-

...for approving the security patch to the bigAPE Backup component. It's a great Joomla backup solution especially for those just learning about site maintenance.

The classes\PEAR.php file does not contain the lines

Code: Select all

/** ensure this file is being included by a parent file */
defined( '_VALID_MOS' ) or die( 'Direct Access to this location is not allowed.' );

Is this safe?

Thanks rliskey-

...for approving the security patch to the bigAPE Backup component.

Please note that we CANNOT "approve" third party code. We are only collecting and passing on information as it is reported to us. Each site administrator is still responsible for deciding if third party code meets their particular site security requirements.

Thanks for all your comments guys, we have been swamped with work over the last two years and we are currently emigrating out to Melbourne, Australia. Our workload will relax within the next few weeks and we will have much more time to put into Joomla. Fear not, we have not forgotten you.

Al