Use-after-free vulnerability in bitlbee-libpurple before 3.5 allows remote servers to cause a denial of service (crash) or possibly execute arbitrary code by causing a file transfer connection to expire.

BitlBee before 3.5 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) and possibly execute arbitrary code via a file transfer request for a contact that is not in the contact list.

Description of problem: Bitlbee 1.2.2 was released, see the following changelog:

Version 1.2.2: - Security bugfix: It was possible to hijack accounts (without gaining access to the old account, it's simply an overwrite) - Some more stability improvements. - Fixed bug where people with non-lowercase nicks couldn't drop their account. - Easier upgrades of non-forking daemon mode servers (using the DEAF command). - Can be cross-compiled for Win32 now! (No support for SSL yet though, which makes it less useful for now.) - Exponential backoff on auto-reconnect. - Changing passwords gives less confusing feedback ("password is empty") now.

Finished 26 Aug 2008

Version-Release number of selected component (if applicable): bitlbee-1.2.1-1

Actual results: bitlbee-1.2.1-1

Expected results: bitlbee-1.2.2-1 ;-)

Additional info: I know, there's a security fix inside, but I'm unable to identify that one.

Description of problem: Bitlbee 1.2.3 was released, see the following changelog:

Version 1.2.3: - Fixed one more flaw similar to the previous hijacking bug, caused by incon- sistent handling of the USTATUSIDENTIFIED state. All code touching these variables was reviewed and should be correct now.

Finished 7 Sep 2008

Version-Release number of selected component (if applicable): bitlbee-1.2.2-1

Actual results: bitlbee-1.2.2-1

Expected results: bitlbee-1.2.3-1 ;-)