CVE-2008-3969: Medium severity bitlbee vulnerability

Published Sep 7, 2008
·
Updated

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 ;-)

Other sources

Multiple unspecified vulnerabilities in BitlBee before 1.2.3 allow remote attackers to "overwrite" and "hijack" existing accounts via unknown vectors related to "inconsistent handling of the USTATUSIDENTIFIED state." NOTE: this issue exists because of an incomplete fix for CVE-2008-3920.

MITRE

Affected Software

3 affected componentsFixes available
redhat/1.2.3<1
1
bitlbee BitlBee<1.2.3
Fedoraproject Fedora=8

Event History

Sep 10, 2008
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2008-3969?

CVE-2008-3969 is categorized as a moderate severity vulnerability affecting Bitlbee 1.2.3.

2

How do I fix CVE-2008-3969?

To fix CVE-2008-3969, upgrade to Bitlbee version 1.2.4 or later.

3

What versions are affected by CVE-2008-3969?

CVE-2008-3969 affects Bitlbee version 1.2.3 and earlier releases.

4

What type of vulnerability is CVE-2008-3969?

CVE-2008-3969 is a vulnerability that involves improper handling of user status, which could lead to information disclosure.

5

Is there a workaround for CVE-2008-3969?

A workaround for CVE-2008-3969 is to restrict the use of the affected version until an upgrade can be performed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203