Geeklog

Changes

This document is intended to give a quick overview over the most important and / or obvious changes. For a detailed list of changes, please consult the ChangeLog. The file docs/changed-files has a list of files that have been changed since the last release.

Geeklog 1.8.2sr1

This release addresses the following security issues:

Other fixes:

Geeklog 1.8.2

Geeklog 1.8.2 is a maintenance release. There were no changes in the database, the templates, or the language files in this release, so upgrades should be straightforward.

Bugfixes

Geeklog 1.8.1

Geeklog 1.8.1 is a maintenance release and a recommended update for all users of Geeklog 1.8.0. There were no changes in the database, the templates, or the language files (other than some updated translations) in this release, so upgrades should be straightforward.

This Geeklog release now ships with jQuery 1.6.3.

Bugfixes

Geeklog 1.8.0

Note: Geeklog 1.8.0 now requires PHP 5.2.0 or later. We will provide legacy PHP 4 support for Geeklog 1.7.2 for a limited time, but would strongly suggest that you switch to PHP 5.2 or later as soon as possible.

For details, please see the announcement on the Geeklog homepage.

New Features and Improvements

Geeklog 1.7.2

Note: Geeklog 1.7.2 is the last Geeklog version to work on PHP 4. We will be providing security fixes, if required, for this version until 2012. New features will only be added to Geeklog 1.8.0 and later versions, which will require at least PHP 5.2.0 to run. Please see the announcement on geeklog.net for details.

Bugfixes

Geeklog 1.7.1sr1

This release fixes an XSS in the admin's configuration panel, reported by Aung Khant of the YGN Ethical Hacker Group.

Geeklog 1.7.1

New Features and Improvements

Bugfixes

Geeklog 1.7.0

New Features and Improvements

Other changes

This release also includes a number of patches and improvements made by students applying for participation in the Google Summer of Code 2010. Thank you!

Geeklog 1.6.1sr2

This release fixes an XSS in the admin's configuration panel, reported by Aung Khant of the YGN Ethical Hacker Group.

Geeklog 1.6.1sr1

This release fixes a vulnerability to dictionary attacks in the autologin, originally reported by Bookoo of the Nine Situations Group.

Geeklog 1.6.1

New Features and Improvements

Please also see the list of theme changes.

Bugfixes

Geeklog 1.6.0sr2

This release addresses the following security issue:

Other fixes:

Geeklog 1.6.0sr1

This release addresses the following security issues:

  1. Gerendi Sandor Attila reported an XSS in the forms to email a user and to email a story to a friend.
  2. The "Mail Story to a Friend" function didn't check story permissions, so that it was possible to email a story even if you didn't have the permissions to view it on the site.

Other fixes:

Geeklog 1.6.0

Results from the Summer of Code

This release incorporates the following projects implemented during the the 2008 Google Summer of Code:

Other changes

This release also includes a number of patches and improvements made by students applying for participation in the Google Summer of Code 2009. Thank you!

Geeklog 1.5.2sr6

This release fixes a vulnerability to dictionary attacks in the autologin, originally reported by Bookoo of the Nine Situations Group.

Geeklog 1.5.2sr5

This release addresses the following security issues:

  1. Gerendi Sandor Attila reported an XSS in the forms to email a user and to email a story to a friend.
  2. The "Mail Story to a Friend" function didn't check story permissions, so that it was possible to email a story even if you didn't have the permissions to view it on the site.

Geeklog 1.5.2sr4

Bookoo of the Nine Situations Group posted another SQL injection exploit, targetting an old bug in usersettings.php. As with the previous issues, this allowed an attacker to extract the password hash for any account and is fixed with this release.

Geeklog 1.5.2sr3

Bookoo of the Nine Situations Group posted another SQL injection exploit, this time targetting the webservices API. As with the previous issue, this allowed an attacker to extract the password hash for any account and is fixed with this release.

Geeklog 1.5.2sr2

Bookoo of the Nine Situations Group posted an SQL injection exploit for glFusion that also works with Geeklog. This issue allowed an attacker to extract the password hash for any account and is fixed with this release.

Geeklog 1.5.2sr1

Fernando Muñoz reported a possible XSS in the query form on most admin panels that we are fixing with this release.

Geeklog 1.5.2

Bugfixes

Fixes in the bundled Plugins

Other Changes

Geeklog 1.5.1

Geeklog 1.5.1 is mostly a bugfix release and a recommended upgrade for users of Geeklog 1.5.0. There were also a few minor feature additions.

Bugfixes

Security related

Other Bugfixes

Fixes in the bundled Plugins

New Features and Improvements

Theme Changes

There was one mandatory theme change: The template file for configuration items, admin/config/config_element.thtml has to be updated (copy from the Professional theme). All other theme changes in this release are optional - see the theme documentation for details.

Geeklog 1.5.0

Results from the Summer of Code

This release incorporates the following projects implemented during the the 2007 Google Summer of Code:

Other New Features and Improvements

Security

Geeklog 1.4.1

New Features

Security

In the light of the security issues discovered in Geeklog 1.4.0 and earlier versions, the Geeklog source code has undergone a code review. We have identified and addressed several minor issues and introduced new measures to enhance security in this release. As a welcome side effect, the code reviews have also uncovered a few bugs and inconsistencies that we also fixed in this release.

Spam Protection

With this release we are finally removing support for the discontinued MT-Blacklist. In its place, we are now using a system called Spam Link Verification (SLV) run by Russ Jones at www.linksleeve.org. SLV could be described as a community-driven, automatically updated blacklist. See the documentation of the Spam-X plugin for details.

Geeklog 1.4.0sr6

MustLive pointed out a possible XSS in the form to email an article to a friend that we're fixing with this release.

Geeklog 1.4.0sr5-1

This release fixes display problems in the comment preview that were only introduced in Geeklog 1.4.0sr5.

Geeklog 1.4.0sr5

JPCERT/CC informed us about a possible XSS in the comment handling that we're fixing with this release.

Geeklog 1.4.0sr4

Two exploits have been released by "rgod" for insecure Geeklog installations and for a bug in the "mcpuk" file manager that we've been shipping as part of FCKeditor in all previous 1.4.0 releases.

Note: This release also includes the updated lib-trackback.php for better protection against Trackback spam.

Geeklog 1.4.0sr3

This release addresses the following security issues:

  1. Possible SQL injection and authentication bypass in auth.inc.php (reported by the Security Science Researchers Institute Of Iran).
  2. Possible XSS in getimage.php (reported by the Security Science Researchers Institute Of Iran).
  3. Path disclosure in getimage.php and the functions.php of some themes, e.g. the Professional theme (reported by the Security Science Researchers Institute Of Iran).
  4. Possible SQL injection in story submissions.

Geeklog 1.4.0sr2

This release addresses the following security issues:

Geeklog 1.4.0sr1

This release addresses the following security issues:

Geeklog 1.4.0

(Geeklog 1.4.0 was originally supposed to be called 1.3.12, so any references you may find to a version 1.3.12 apply to version 1.4.0)

New Features

Compatibility

More Information

We have posted a series of stories on the Geeklog homepage that highlight and explain some of the new features:

Geeklog 1.3.11sr7

JPCERT/CC informed us about a possible XSS in the comment handling that we're fixing with this release.

Geeklog 1.3.11sr6

This release addresses the following security issues:

  1. Possible SQL injection and authentication bypass in auth.inc.php (reported by the Security Science Researchers Institute Of Iran).
  2. Possible XSS in getimage.php (reported by the Security Science Researchers Institute Of Iran).
  3. Path disclosure in getimage.php and the functions.php of some themes, e.g. the Professional theme (reported by the Security Science Researchers Institute Of Iran).
  4. Possible SQL injection in story submissions.

Geeklog 1.3.11sr5

Geeklog 1.3.11sr4

This release addresses the following security issues:

Geeklog 1.3.11sr3

This release addresses the following security issues:

  1. Provided you knew the story id, it was possible to submit comments for stories even if you did not have access to those stories (reported by LWC). The same problem also existed with poll comments.
  2. Supplying an illegal start or end date to the advanced search resulted in a warning message that disclosed the path to the Geeklog install on the server (reported by r0t3d3Vil).
    It was not possible to use this for SQL injections.

Also included in this release are bugfixes, e.g. for the problems editing static pages when URL rewriting was enabled, that were introduced in 1.3.11sr2.

Geeklog 1.3.11sr2

This release provides security enhancements and better spam protection originally developed for Geeklog 1.3.12. It also addresses a few bugs where the bugfix could be integrated with a reasonable amount of work (other bugfixes will have to wait for the 1.3.12 release).

Security and Spam protection

Please note that MT-Blacklist (used by Spam-X) has recently been discontinued. The Spam-X plugin as included in this release is configured to get the last version of the blacklist from geeklog.net, but there will be no more updates.

Bugfixes

For a complete list of bugfixes, please see the Changelog.

Improvements

Geeklog 1.3.11sr1

This release addresses the following security issue:

Geeklog 1.3.11

Geeklog 1.3.11 is a bugfix and security release over Geeklog 1.3.10 and is meant to replace 1.3.10. The change in the version number was necessary since one of the bugfixes involves a change in the database.

Security issues

  1. It was possible to submit stories anonymously even if anonymous submissions were turned off in config.php (reported by Barry Wong).
    These stories still ended up in the submission queue, though, unless you disabled it in config.php.
  2. Some of the parameters in link and event submissions weren't filtered, leaving them open to potential SQL injections.
  3. The links for the What's Related block were created from the unfiltered story text, opening the possibility of XSS attacks (reported by Vincent Furia).

Bugfixes

We strongly advise users of Geeklog 1.3.10 to upgrade to 1.3.11 ASAP. Upgrading should be relatively painless, as there weren't any changes in the themes, language files, or config.php over 1.3.10.

Geeklog 1.3.10

New Default Theme

This release comes with a new default theme: We've chosen the Professional theme, kindly provided by Victor B. Gonzalez (of Aeonserv fame). The theme has been modified slightly and is now fully HTML 4.01 and CSS compliant.

We've also decided to remove the old set of themes (Classic, Clean, Digital Monochrome, Gameserver, Smooth Blue, XSilver, Yahoo) from the distribution. They are now available as a separate tarball.

New Features

Other Improvements

Comments

Security-related fixes

Note: All of the following bugs were problems with Geeklog's permissions system and fall into the "information leakage" category, i.e. under certain circumstances, site content was visible to persons who shouldn't be able to see it. None of these bugs were exploitable in the sense that they could be used to gain privileges or cause damage to Geeklog or the environment it's running in.

Other bugfixes

Please note that there have also been theme changes, some of which are important to make the new features work (e.g. the editable story IDs and the story archive options)!

This release contains various improvements provided by the Geeklog community (see the docs/history file for proper credits). Thank you!

Geeklog 1.3.9sr3

This release addresses the following security issues:

  1. It was possible to submit stories anonymously even if anonymous submissions were turned off in config.php (reported by Barry Wong).
    These stories still ended up in the submission queue, though, unless you disabled it in config.php.
  2. Some of the parameters in link and event submissions weren't filtered, leaving them open to potential SQL injections.

Geeklog 1.3.9sr2

This release addresses the following security issues:

  1. Fixed a cross site scripting vulnerability caused by using the variable $topic in the language files (bug #293).
  2. Prevent comment posts on stories or polls were comment posting has been disabled.

Other fixes

Geeklog 1.3.9sr1

This release addresses the following security issues:

  1. It was possible to post anonymous comments, even when anonymous comment posting had been switched off in config.php.
    This bug was apparently exploited by spammers to send hundreds of spam posts to certain Geeklog sites.
  2. Added additional speed limit checks for comments and submissions.
  3. If none of the topics were visible for anonymous users, the site's index page may still have displayed some stories for anonymous users, depending on the stories' permissions.
  4. Users still got Daily Digest emails for topics from which they had been removed (bug #178).
  5. It was possible to subscribe to the Daily Digest for all topics, even if the user did not have access to certain topics.
  6. Comments to stories were sometimes listed in a user's profile, even if the user viewing the profile didn't have permissions to access the story the comments belonged to.

Other fixes

Geeklog 1.3.9

New Features

Please see the themes documentation for a complete list of theme changes.

Also included is the Static Pages plugin 1.4, which now has, among other improvements, a second option to include PHP in static pages without having to use the PHP return statement.

Bugfixes

There have also been a lot of changes to improve security, especially against SQL injections.

Geeklog 1.3.8-1sr6

This release addresses the following security issues:

  1. Fixed a cross site scripting vulnerability caused by using the variable $topic in the language files (bug #293).
  2. Prevent comment posts on stories or polls were comment posting has been disabled.

Geeklog 1.3.8-1sr5

This release addresses the following security issue:

  1. It was possible to post anonymous comments, even when anonymous comment posting had been switched off in config.php.
    This bug was apparently exploited by spammers to send hundreds of spam posts to certain Geeklog sites.

Geeklog 1.3.8-1sr4

This release addresses the following security issues:

  1. It was possible for users in the Group Admin and User Admin groups to become a member of the Root group (reported by Samuel M. Stone, bug #135).
  2. Being admin for a certain area (e.g. Story Admin for stories) made it possible to delete all objects in that area (e.g. stories) even if the user was not supposed to have access to them, provided the id of the object was known.
  3. It was possible to delete other people's personal events if you knew the event ID.
  4. It was possible to browse through the comments of a story even if the user did not have access to the actual story (reported by Peter Roozemaal).
  5. Due to an XSS issue, it was possible to change someone's account settings (including the password) if you got them to click on a specially crafted link (reported by Jelmer, fix suggested by Vincent Furia).
  6. The comment display suffered from the possibility of an SQL injection (reported by Jelmer).
  7. It was possible to inject Javascript code in the calendar (reported by Jelmer).
  8. It was possible to execute (but not save) Javascript code in the comment preview (reported by Jelmer).

Geeklog 1.3.8-1sr3

This release addresses the following security-related issues:

  1. As "dr.wh0" pointed out, the category field for link submissions was not filtered at all. Although you probably can't cause too much harm with those 32 characters, this has now been fixed.
  2. Vincent Furia found that the restrictions for the form to email users could be circumvented and could even be used to spam users. In addition to fixing theses issues, there is now also a speed limit on that form (defaults to the speed limit for story submissions).
  3. There was a way to post comments anonymously even when posting for anonymous users had been disabled.
  4. It was possible to post comments under someone else's username.

Geeklog 1.3.8-1sr2

Jouko Pynnonen found a way to trick the new "forgot password" feature, introduced in 1.3.8, into letting an attacker change the password for any account. This release addresses this issue - there were no other changes.

Obviously, we strongly recommend to upgrade as soon as possible.

Geeklog 1.3.8-1sr1

The purpose of this release is to address some of the security issues reported in September and early October 2003. We strongly recommend upgrading to this version.

Security issues

  1. By including Ulf Harnhammar's kses HTML filter, this release addresses a variety of possible Javascript injection and CSS defacement issues.
  2. Details of SQL errors will not be reported in the browser any more (but only in Geeklog's error.log file). This will avoid disclosing any sensitive information as part of the error message (which is so far the only problem we have found with the alleged SQL injection issues that have been reported).

Please note that at the moment we do not recommend to use Geeklog with MySQL 4.1 (which, at the time of this writing, is in alpha state and should not be used on production sites anyway). An upcoming release of Geeklog will include more thorough filtering of SQL injections attempts, thus also fixing the problems with MySQL 4.1.

Other fixes

Geeklog 1.3.8-1

Geeklog 1.3.8-1 is a bugfix release over Geeklog 1.3.8. It contains a variety of (mostly minor) bugfixes. None of those fixes are security-related.

Bugfixes

The full 1.3.8-1 tarball also includes new and updated language files (see the Changelog for details).

Geeklog 1.3.8

New Features

Geeklog 1.3.8 Includes the Static Pages 1.3 plugin which replaces both the Static Pages 1.1 and 1.2 plugins. See the Static Pages documentation for details.

Bugfixes

Geeklog 1.3.7sr5

This release addresses the following security issues:

  1. It was possible for users in the Group Admin and User Admin groups to become a member of the Root group (reported by Samuel M. Stone, bug #135).
  2. Being admin for a certain area (e.g. Story Admin for stories) made it possible to delete all objects in that area (e.g. stories) even if the user was not supposed to have access to them, provided the id of the object was known.
  3. It was possible to delete other people's personal events if you knew the event ID.
  4. It was possible to browse through the comments of a story even if the user did not have access to the actual story (reported by Peter Roozemaal).
  5. Due to an XSS issue, it was possible to change someone's account settings (including the password) if you got them to click on a specially crafted link (reported by Jelmer, fix suggested by Vincent Furia).
  6. The comment display suffered from the possibility of an SQL injection (reported by Jelmer).
  7. It was possible to inject Javascript code in the calendar (reported by Jelmer).
  8. It was possible to execute (but not save) Javascript code in the comment preview (reported by Jelmer).

Geeklog 1.3.7sr4

This release addresses the following security-related issues:

  1. As "dr.wh0" pointed out, the category field for link submissions was not filtered at all. Although you probably can't cause too much harm with those 32 characters, this has now been fixed.
  2. Vincent Furia found that the restrictions for the form to email users could be circumvented and could even be used to spam users.
  3. There was a way to post comments anonymously even when posting for anonymous users had been disabled.
  4. It was possible to post comments under someone else's username.

Geeklog 1.3.7sr3

The purpose of this release is to address some of the security issues reported in September and early October 2003. If you don't plan to upgrade to the latest version of Geeklog (1.3.8-1sr1, at the time of this writing), we strongly suggest you upgrade to at least 1.3.7sr3 instead.

Security issues

  1. By including Ulf Harnhammar's kses HTML filter, this release addresses a variety of possible Javascript injection and CSS defacement issues.
  2. Details of SQL errors will not be reported in the browser any more (but only in Geeklog's error.log file). This will avoid disclosing any sensitive information as part of the error message (which is so far the only problem we have found with the alleged SQL injection issues that have been reported).

Please note that at the moment we do not recommend to use Geeklog with MySQL 4.1 (which, at the time of this writing, is in alpha state and should not be used on production sites anyway). An upcoming release of Geeklog will include more thorough filtering of SQL injections attempts, thus also fixing the problems with MySQL 4.1.

Geeklog 1.3.7sr2

Security issues

The purpose of this release is to fix the following security issues. All users are strongly encouraged to upgrade to this version ASAP.

  1. It was possible to obtain valid session ids for every account on a Geeklog site, including the Admin account (reported by SCAN Associates).
  2. Using Internet Explorer, it was possible to upload an image with embedded PHP code and execute it (reported by SCAN Associates).
  3. Story permissions could override topic permissions, resulting in the display of stories to users who shouldn't have access to them (reported by Andrew Lawlor). This was already fixed with the new index.php, released 2003-05-15.
  4. Added a warning in config.php that adding any of the following tags to the list of allowable HTML can make the site vulnerable to scripting attacks:
    <img> <span> <marquee> <script> <embed> <object> <iframe>
    (pointed out by Joat Dede).

This update also includes fixes for the notorious "permission denied" error messages that some users would get in the Admin area (e.g. when trying to save a story and being "only" a user with Story Admin permissions).

The full 1.3.7sr2 tarball also includes various new and updated language files (see the Changelog for details).

Geeklog 1.3.7sr1

Security issues

The main purpose of this release is to fix the following security issues. All users are strongly recommended to upgrade to this version.

  1. Javascript code could be injected in the homepage field of a user's profile (reported by Jin Yean Tan).
  2. Javascript code could be injected in certain URLs to be used in a cross-site scripting attack (reported by Jin Yean Tan).
  3. Comments could be deleted by anybody if they knew the comment id (which is not normally visible).
  4. A StoryAdmin could manipulate stories even if s/he did not have access to them (e.g. when s/he was not a member of a certain group). The same applied to Admins for events, links, polls, topics, and blocks (reported by Kobaz).

Other Bugfixes

Documentation and hard-coded links (version check, link to Geeklog in a site's footer) have been updated to point to www.geeklog.net.

Geeklog 1.3.7

New Features

Bugfixes

Contributors: Blaine Lang, Vincent Furia, and Kenn Osborne have contributed to this release. Thank you!

Speeding up Geeklog (a bit)

If you're upgrading from 1.3.6 or older versions, you may want to run the script called addindex.php that you will find in the install directory. This script adds index fields to some of Geeklog's database tables which should improve overall access times a bit.

This has been implemented as a separate script (and not as part of the upgrade process of the install script) since it may take some time to run, depending on how many users / stories / etc. you have in your database. Some people may even run into timeouts, e.g. when their hosting service limits the execution time of PHP scripts. If that happens to you - Don't Panic. Simply run the script again (and again and ...) until it reports that it didn't add any fields to any tables.

Please note that you do not need to run this script if you're doing a fresh install of Geeklog 1.3.7. A database created during a fresh install already has the new index fields.

Geeklog 1.3.6

New Features

Bugfixes

Notes

Contributors: Gene Wood, Blaine Lang, Tom Willet, and Roger Webster have contributed to this release. Thank you!