This feed provides announcements of resolved security issues in Joomla! software releases.

For more information about the Joomla! Security Strike Team (JSST) and its processes, please review our Security article.

To report potential security issues, please follow the guidelines in the above referenced article. Please note that we are only able to provide support for the Joomla! CMS, Joomla! Framework, and *.joomla.org network of websites.

You can subscribe to notifications from this feed through a RSS reader or email notifications via FeedBurner.

  • Project: Joomla!
  • SubProject: All
  • Severity: Medium
  • Versions: 1.7.0 and all 1.6.x versions
  • Exploit type: XSS
  • Reported Date: 2011-August-02
  • Fixed Date: 2011-September-22

Description

Inadequate escaping leads to XSS vulnerability in com_search.

Affected Installs

Joomla! version 1.7.0 and all 1.6.x versions

Solution

Upgrade to the latest Joomla! version (1.7.1 or later)

Contact

The JSST at the Joomla! Security Centre.

Reported By: Aung Khant
  • Project: Joomla!
  • SubProject: All
  • Severity: Medium
  • Versions: 1.7.0 and all 1.6.x versions
  • Exploit type: XSS
  • Reported Date: 2011-August-02
  • Fixed Date: 2011-September-22

Description

Inadequate escaping leads to XSS vulnerability in back end.

Affected Installs

Joomla! version 1.7.0 and all 1.6.x versions

Solution

Upgrade to the latest Joomla! version (1.7.1 or later)

Contact

The JSST at the Joomla! Security Centre.

Reported By: Aung Khant
  • Project: Joomla!
  • SubProject: All
  • Severity: Medium
  • Versions: 1.6.5 and all earlier 1.6.x versions
  • Exploit type: XSS
  • Reported Date: 2011-July-11
  • Fixed Date: 2011-July-19

Description

Inadequate escaping leads to XSS vulnerability.

Affected Installs

Joomla! version 1.6.5 and all earlier 1.6.x versions

Solution

Upgrade to the latest Joomla! version (1.6.6 or later)

Contact

The JSST at the Joomla! Security Centre.

Reported By: Aung Khant
  • Project: Joomla!
  • SubProject: All
  • Severity: Low
  • Versions: 1.6.3 and all earlier 1.6.x versions
  • Exploit type: Information Disclosure
  • Reported Date: 2011-May-25
  • Fixed Date: 2011-June-23

Description

Inadequate filtering causes possible information disclosure.

Affected Installs

Joomla! version 1.6.3 and all earlier 1.6.x versions

Solution

Upgrade to the latest Joomla! version (1.6.4 or later)

Contact

The JSST at the Joomla! Security Centre.

Reported By: Aung Khant
  • Project: Joomla!
  • SubProject: All
  • Severity: Medium
  • Versions: 1.6.3 and all earlier 1.6.x versions
  • Exploit type: XSS
  • Reported Date: 2011-May-25
  • Fixed Date: 2011-June-27

Description

Inadequate filtering leads to XSS vulnerability.

Affected Installs

Joomla! version 1.6.3 and all earlier 1.6.x versions

Solution

Upgrade to the latest Joomla! version (1.6.4 or later)

Contact

The JSST at the Joomla! Security Centre.

Reported By: Aung Khant
  • Project: Joomla!
  • SubProject: All
  • Severity: Low
  • Versions: 1.5.15 and all previous 1.5 releases
  • Exploit type: Unauthorised Access
  • Reported Date: 2010-Jan-07
  • Fixed Date: 2010-Apr-23

Description

When a user requests a password reset, the reset tokens were stored in plain text in the database. While this is not a vulnerability in itself, it allows user accounts to be compromised if there is an extension on the site with an SQL injection vulnerability.

Affected Installs

All 1.5.x installs prior to and including 1.5.15 are affected.

Solution

Upgrade to the latest Joomla! version (1.5.16 or later)

Contact

The JSST at the Joomla! Security Centre.

Reported By: Madis Abel
  • Project: Joomla!
  • SubProject: All
  • Severity: Moderate
  • Versions: 1.5.15 and all previous 1.5 releases
  • Exploit type: Session fixation
  • Reported Date: 2010-Mar-25
  • Fixed Date: 2010-Apr-23

Description

Session id doesn't get modified when user logs in.  A remote site may be able to forward a visitor to the Joomla! site and set a specific cookie.  If the user then logs in, the remote site can use that cookie to authenticate as that user.

Affected Installs

All 1.5.x installs prior to and including 1.5.15 are affected.

Solution

Upgrade to the latest Joomla! version (1.5.16 or later)

Contact

The JSST at the Joomla! Security Centre.

Reported By: Raúl Siles and Steven Pignataro
  • Project: Joomla!
  • SubProject: All
  • Severity: Low
  • Versions: 1.5.15 and all previous 1.5 releases
  • Exploit type: Code upload
  • Reported Date: 2009-Dec-30
  • Fixed Date: 2010-Apr-23

Description

The migration script in the Joomla! installer does not check the file type being uploaded. If the installation application is present, an attacker could use it to upload malicious files to a server.

Affected Installs

All 1.5.x installs prior to and including 1.5.15 are affected.

Solution

Upgrade to the latest Joomla! version (1.5.16 or later)

Contact

The JSST at the Joomla! Security Centre.

Reported By: Nicola Bettini
  • Project: Joomla!
  • SubProject: All
  • Severity: Moderate
  • Versions: 1.5.15 and all previous 1.5 releases
  • Exploit type: information Disclosure
  • Reported Date: 2010-Feb-21
  • Fixed Date: 2010-Apr-23

Description

If a user entered a URL with a negative query limit or offset, a PHP notice would display revealing information about the system.

Affected Installs

All 1.5.x installs prior to and including 1.5.15 are affected.

Solution

Upgrade to the latest Joomla! version (1.5.16 or later)

Contact

The JSST at the Joomla! Security Centre.

Reported By: Security List
  • Project: Joomla!
  • SubProject: All
  • Severity: Low
  • Versions: 1.5.14 and all previous 1.5 releases
  • Exploit type: Extension Version Disclosure
  • Reported Date: 2009-October-13
  • Fixed Date: 2009-Nov-03

Description

It is possible to read the contents of an extension's XML file and find the version number of the installed extension. This could allow people to exploit a known security flaws for a specific version of an extension.

Affected Installs

All 1.5.x installs prior to and including 1.5.14 are affected.

Solution

Turn on Apache mod_rewrite and configure your .htaccess file to filter out XML files. In the htaccess.txt file shipped with version 1.5.15, lines 35-39 contain example code that will deny access to XML files. You can incorporate this code (or similar code) into your .htaccess file. Be sure to test that it does not cause problems on your site.

Contact

The JSST at the Joomla! Security Centre.

Reported By: WHK and Gergő Erdősi