Security Patch for XOOPS 2.5.6
As always, security is on top of priority list of XOOPS!
Current users of XOOPS 2.5.6 are encouraged to download and apply a Security Patch.
Download: SourceForge File Repository
This security patch fixes some potential XSS issues discovered by Mehdi Dadkhah and fixed by Richard Griffith.
While 2.5.6 Websites that have currently installed Protector are safe from this XSS vulnerability, we recommend strongly to apply this patch to ALL XOOPS 2.5.6 Websites.
It is not enough to stress that you should ALWAYS have Protector installed!!!
How to Apply the Patch:
--------------------------
You will need as minimum PHP 5.3.7
Just copy ALL the files from /htdocs folder in this Zip file to your XOOPS Website.
No other action is needed.
==============================================
For users of XOOPS Versions older than 2.5.6
==============================================
Please update AS SOON AS POSSIBLE to XOOPS 2.5.6. As always, the current versions are always the most stable and safest, i.e. older versions might be open to vulnerabilities that has been already fixed in the current version.
As of today, all XOOPS 2.5.6 versions available for download have been all patched.
Wishing everybody Happy and Safe Xoopsing!
XOOPS Core Team
2013-09-24
Read more... | 11 comments
Current users of XOOPS 2.5.6 are encouraged to download and apply a Security Patch.
Download: SourceForge File Repository
This security patch fixes some potential XSS issues discovered by Mehdi Dadkhah and fixed by Richard Griffith.
While 2.5.6 Websites that have currently installed Protector are safe from this XSS vulnerability, we recommend strongly to apply this patch to ALL XOOPS 2.5.6 Websites.
It is not enough to stress that you should ALWAYS have Protector installed!!!
How to Apply the Patch:
--------------------------
You will need as minimum PHP 5.3.7
Just copy ALL the files from /htdocs folder in this Zip file to your XOOPS Website.
No other action is needed.
==============================================
For users of XOOPS Versions older than 2.5.6
==============================================
Please update AS SOON AS POSSIBLE to XOOPS 2.5.6. As always, the current versions are always the most stable and safest, i.e. older versions might be open to vulnerabilities that has been already fixed in the current version.
As of today, all XOOPS 2.5.6 versions available for download have been all patched.
Wishing everybody Happy and Safe Xoopsing!
XOOPS Core Team
2013-09-24
Security Patch for XOOPS 2.5.5
Current users of XOOPS 2.5.5 are encouraged to download and apply a Security Patch.
This patch is included in the upcoming XOOPS 2.5.6, which should be released in the next couple of weeks, after the testing of the Beta version is done.
Download: SourceForge File Repository
Read more... | 11 comments
This patch is included in the upcoming XOOPS 2.5.6, which should be released in the next couple of weeks, after the testing of the Beta version is done.
Download: SourceForge File Repository
Security Patch for XOOPS 2.3.3
As discussed previously in forums, there are potential vulnerabilities identified in:
a) PM
b) Protector
modules.
While (a) is addressed by having Protector installed, and (b) is addressed by having "register_globals" disabled and having XOOPS_TRUST_PATH outside of the Document Root, we've addressed the issues in XOOPS 2.4.
However, since we don't know when exactly we'll release XOOPS 2.4, we're releasing this Security Patch for XOOPS 2.3.3 users.
Download: SourceForge XOOPS.
Installation: See the ReadMe.txt file
You are highly encouraged to implement the patch to your existing XOOPS 2.3.3 system.
Special thanks to Trabis, who addressed these issues.
Read more... | 21 comments
a) PM
b) Protector
modules.
While (a) is addressed by having Protector installed, and (b) is addressed by having "register_globals" disabled and having XOOPS_TRUST_PATH outside of the Document Root, we've addressed the issues in XOOPS 2.4.
However, since we don't know when exactly we'll release XOOPS 2.4, we're releasing this Security Patch for XOOPS 2.3.3 users.
Download: SourceForge XOOPS.
Installation: See the ReadMe.txt file
You are highly encouraged to implement the patch to your existing XOOPS 2.3.3 system.
Special thanks to Trabis, who addressed these issues.
Vulnerability in Protector if placed in DocumentRoot
We've been made aware of a vulnerability of the Protector, if placed in the DocumentRoot
This is for all versions of XOOPS, if the XOOPS_TRUST_PATH (or xoops_lib) directory that contains the Protector, is placed in the DocumentRoot
As we've always communicated to you (e.g. in this article A Guide to Make your XOOPS Installation even more secure), the best solution is to place your xoops_lib folder outside of webroot path. You should also change the name of xoops_lib to something different, and modify the mainfile.php accordingly.
If you are not allowed to do so, add .htaccess to protect your Protector module:
The .htaccess should be placed in /xoops_lib or whatever the name of your XOOPS_TRUST_PATH is.
If .htaccess is not allowed or enabled on your server, turn off global_register on your server.
If you are not allowed to do any of the above, then the only solution is to remove Protector module from your server and wait for a complete fix of the module.
Of course, the best scenario would be to have clean and safe code. Unfortunately, we've missed this security bug, but we're working on the solution and will release it soon.
Read more... | 10 comments
This is for all versions of XOOPS, if the XOOPS_TRUST_PATH (or xoops_lib) directory that contains the Protector, is placed in the DocumentRoot
As we've always communicated to you (e.g. in this article A Guide to Make your XOOPS Installation even more secure), the best solution is to place your xoops_lib folder outside of webroot path. You should also change the name of xoops_lib to something different, and modify the mainfile.php accordingly.
If you are not allowed to do so, add .htaccess to protect your Protector module:
order deny,allow
deny from all The .htaccess should be placed in /xoops_lib or whatever the name of your XOOPS_TRUST_PATH is.
If .htaccess is not allowed or enabled on your server, turn off global_register on your server.
If you are not allowed to do any of the above, then the only solution is to remove Protector module from your server and wait for a complete fix of the module.
Of course, the best scenario would be to have clean and safe code. Unfortunately, we've missed this security bug, but we're working on the solution and will release it soon.
XOOPS 2.3.2b - Security Release
The security is always on top of the list of XOOPS Developers. Therefore the XOOPS Development Team is pleased to announce the release of XOOPS 2.3.2b, an improved XOOPS 2.3.x release.
This release is solely for a couple of critical fixes, including an XSS vulnerability reported by Digital Sercurity Research Group (or DSRG), potential local file inclusion vulnerability reported by DSRG, autologin bug reported by Dylian, a backward bug in data synchronization reported by boy0917 as well as a bug in xoopsmailer reported by ezsky.
In the 2.3.2b release we have further improved security fixes with help from DSRG.
All XOOPS 2.3.x users are highly recommended to upgrade to this version ASAP.
XOOPS 2.0 and 2.2 versions are not vulnerable to the XSS issues addressed here. However, all 2.0 and 2.2 users who have the Protector module installed are advised to upgrade to the version included in this package for local file inclusion issues.
Download from Sourceforge repository.
Read more... | 10785 bytes more | 37 comments
This release is solely for a couple of critical fixes, including an XSS vulnerability reported by Digital Sercurity Research Group (or DSRG), potential local file inclusion vulnerability reported by DSRG, autologin bug reported by Dylian, a backward bug in data synchronization reported by boy0917 as well as a bug in xoopsmailer reported by ezsky.
In the 2.3.2b release we have further improved security fixes with help from DSRG.
All XOOPS 2.3.x users are highly recommended to upgrade to this version ASAP.
XOOPS 2.0 and 2.2 versions are not vulnerable to the XSS issues addressed here. However, all 2.0 and 2.2 users who have the Protector module installed are advised to upgrade to the version included in this package for local file inclusion issues.
Download from Sourceforge repository.
Protector Security Fix for XOOPS 2.0.x and 2.2.x users
Security is always the highest priority for XOOPS, and therefore we are releasing Security Updates as soon as we find a viable solution.
This is a temporary quick fix for Protector module, addressing potential local file inclusion vulnerability reported by DSRG. We hope that GIJOE, the author of Protector, will address this issue in future releases.
It is included in XOOPS 2.3.2a Security release, but if you're using Protector on XOOPS 2.0.x or 2.2.x, and your XOOPS_TRUST_PATH is located inside the Root, you are advised to upgrade to the version included in this package.
If your XOOPS_TRUST_PATH is outside of the Root (as you should!), you're not affected by this vulnerability.
For more information on how to make your XOOPS installation more secure, please read this article
Download the fix here
XOOPS Development Team
November 28th, 2008
Read more... | 14 comments
This is a temporary quick fix for Protector module, addressing potential local file inclusion vulnerability reported by DSRG. We hope that GIJOE, the author of Protector, will address this issue in future releases.
It is included in XOOPS 2.3.2a Security release, but if you're using Protector on XOOPS 2.0.x or 2.2.x, and your XOOPS_TRUST_PATH is located inside the Root, you are advised to upgrade to the version included in this package.
If your XOOPS_TRUST_PATH is outside of the Root (as you should!), you're not affected by this vulnerability.
For more information on how to make your XOOPS installation more secure, please read this article
Download the fix here
XOOPS Development Team
November 28th, 2008
XOOPS 2.3.2a - Security Release
The XOOPS Development Team is pleased to announce the release of XOOPS 2.3.2a
This release is solely for a couple of critical security fixes, including an XSS vulnerability reported by Digital Research Group, potential local file inclusion vulnerability reported by DSG, Autologin bug reported by Dylian and a backward bug in data synchronization reported by boy0917.
All XOOPS 2.3.x users are highly recommended to upgrade to this version ASAP.
XOOPS 2.0 and 2.2 versions are not vulnerable to the security issues addressed here. However, all 2.0 and 2.2 users who have the Protector module installed are advised to upgrade to the version included in this package.
Download from Sourceforge repository.
Read more... | 10370 bytes more | 48 comments
This release is solely for a couple of critical security fixes, including an XSS vulnerability reported by Digital Research Group, potential local file inclusion vulnerability reported by DSG, Autologin bug reported by Dylian and a backward bug in data synchronization reported by boy0917.
All XOOPS 2.3.x users are highly recommended to upgrade to this version ASAP.
XOOPS 2.0 and 2.2 versions are not vulnerable to the security issues addressed here. However, all 2.0 and 2.2 users who have the Protector module installed are advised to upgrade to the version included in this package.
Download from Sourceforge repository.
A Guide to Make your XOOPS Installation even more secure
The reason for writing this guide is NOT because XOOPS CMS-system isn’t secure enough.
Read more... | 24352 bytes more | 21 comments
It’s written to give new XOOPS'ers a chance to make, with a few changes, a secure installation even more secure. We believe, that existing users also can use the guide, for securing an already installed XOOP website.
This guide is written for XOOPS version 2.3.3RC as Core-version.
Security Update for Bluemoon Modules
We found XSS valnabirity at our sources.
Backpack v0.91 or before
Bmsurvey v0.84 or before
Newbb_fileup v1.83 or before
News_embed v1.44 ( news_fileup ) or before
Popnupblog v3.19 or before
If you are using those scripts we recommend update immediately.
Jump to vendor site
Read more... | 3 comments
Backpack v0.91 or before
Bmsurvey v0.84 or before
Newbb_fileup v1.83 or before
News_embed v1.44 ( news_fileup ) or before
Popnupblog v3.19 or before
If you are using those scripts we recommend update immediately.
Jump to vendor site
WF-Sections V2: New Exploits and Security Issues (Users MUST READ this)
As always, XOOPS developers are committed to ensuring the highest security of XOOPS code. The message below comes from Catzwolf:
Quote:
To follow the story, please visit our discussion Forum.
Read more... | 1 comment
Quote:
If you are still using WF-Sections v1+ and v2+ then I suggest that you read this please.
It has come to my attention that there is a few very bad security exploits that some people could use to gain access to your website. I suggest that all users of this module should either:
1. Deactivate the module for the time being (recommended) or..
2. Renaming XOOPS_ROOT_PATH/modules/wfsections/ratefile.php and print.php.
I am now in the process of doing a full audit of all the WF-Sections code and closing these and all possible security risks that may arise in the future.
I will keep you all posted on an update.
John (AkA Catzwolf)
To follow the story, please visit our discussion Forum.
Login
Search
Recent Comments
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Nov 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|
Latest GitHub Commits
Archives
News archives
- January 2017
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- July 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- March 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- September 2013
- August 2013
- July 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- January 2013
- December 2012
- November 2012
- October 2012
- September 2012
- August 2012
- July 2012
- June 2012
- May 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- April 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- October 2003
- September 2003
- August 2003
- July 2003
- June 2003
- May 2003
- April 2003
- March 2003
- February 2003
- January 2003
- December 2002
- November 2002
- October 2002
- September 2002
- August 2002
- July 2002
- June 2002
- May 2002
- April 2002
- March 2002
- February 2002
- January 2002
- December 2001
- December 1969