Gadgets and Gizmos World

Did you know that WordPress 2.2.1 has 7 (seven) vulnerabilities (see 1st quote below)? Wordpress.org recommends you to upgrade a.s.a.p to version 2.2.3. Unfortunately, some of your favorites plug-in may or may not work in the new version. WordPress.org has a list of known working and not working plug-ins for v2.2.3, and again, unfortunately the list is still short, some of the most popular plug-ins are still not listed. So what you can do is just trying to upgrade and pray for the best. FYI, the Ultimate Tag Warrior v3.141592 and Similar Posts v2.1.0b plug-in fall into the “Plugins that don’t work or are not working properly” category, too bad!

To upgrade or not to upgrade, that’s the question. A security expert from Germany, Benjamin Flesch, has created a “worm” that actually fixes those security holes. That’s a very cool idea, but you need to give him a lot of trust and faith. The idea of executing a worm from someone’s link is really give me a chill, but apparently we don’t have too much choices here. In short we have three options here: one, live with the vulnerabilities and pray that no hackers (or crackers) will exploit your blog (hey, they can defacing your blog, posting some funny jokes, or, God forbid, delete your star PR-9 posts). Two, upgrade to WordPress v2.2.3 and hope that your theme and your plug-ins are all working as before. Three, trust Benjamin and run the worm (see 2nd quote below). It’s your choice. So “pick your poison” (see 3rd quote below) I think I’ll pick number three. Good luck!

Security vulnerabilities in the latest Wordpress v2.2.1

1. Wordpress Persistant XSS Vulnerability in the Default Theme (v.2.2)
Affected Script: /themes.php?page=functions.php
“Header Image and Color” section of the Default Theme Kubrick.
Severity: HIGH - Attack needs no authentication.
Affected Wordpress Build: 2.2
WARNING: This issue may lead to a full blog compromise if the default theme is enabled!

2. Wordpress /options.php SQL Injection Vulnerability
Affected Scripts: All Wordpress files referencing /options.php in a form field, this includes:
* /options-general.php
* /options-writing.php
* /options-reading.php
* /options-discussion.php
* /options-privacy.php
* /options-permalink.php
* /options-misc.php
Severity: LOW - Attacker needs Admininstrator Privileges or valid _wpnonce.
Affected Wordpress Version: 2.2.1 - the latest version (This is a 0day Vulnerability)

3. Wordpress /options.php Information Disclosure
Severity: MEDIUM - All Blog Options are listed on a single page and may be accessed for example via XSS
Affected Wordpress Version: 2.2.1 - the latest version (This is a 0day Vulnerability)

4. Wordpress /options.php Persistant XSS Vulnerability
Severity: MEDIUM - Persistant XSS in the Admin Panel, nevertheless, the Attacker needs Admininstrator Privileges or valid _wpnonce.
Affected Wordpress Version: 2.2.1 - the latest version (This is a 0day Vulnerability)

5. Wordpress /edit-comments.php Database Error (Bug)
Severity: NONE
Affected Wordpress Version: 2.2.1 - the latest version

6. Wordpress /link-import.php XSS Vulnerability
Severity: LOW - Attacker needs Admininstrator Privileges or valid _wpnonce.
Affected Wordpress Version: 2.2.1 - the latest version (This is a 0day Vulnerability)

7. Wordpress /upload.php XSS Vulnerability
Severity: HIGH - Attack needs no authentication.
Affected Wordpress Version: 2.2.1 - the latest version (This is a 0day Vulnerability)
WARNING: This issue may lead to a full blog compromise.

Source

Most of those vulnerabilities need administrative privileges to run. You may ask why we need to care for a “security hole” that needs admin privileges to run. The answer is Yes, it’s a real threat, because you may install a compromise plug-in from somewhere, or click a link that will execute the worm. Benjamin shows this problem very intelligibly with his “worm”.

How to Use the Worm to Fix the Vulnerabilities

Go to your blog and login to your Wordpress Adminstration Panel
Post a Comment to your own Blog containing a link to this blog, that means http://mybeni.rootzilla.de/mybeNi/
Go into your admin Panel -> Moderate Comments and click the freaking link :o)
The friendly worm will guide you through everything and your blog is secure again.

Source

Origin of the “pick your poison” phrase

The origin is simply that since the mid-19th century “poison” has been slang for alcoholic drink (in Australia a pub was known as a “poison-shop”). This may refer to the Latin root “toxicum” (meaning “poison”) of the word “intoxicate”, or it may just be a reference to the bad effects of excessive drinking. Thus the phrases “what’s your poison?” “Pick your poison” and “choose your poison” arose naturally.