Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-5668: bitlbee-libpurple before 3.5.1 allows remote attackers to cause a denial of service (NULL pointer dereference

61
This week
CRITICAL 9.8REMOTEUPGRADEUPGRADE

CVE-2017-5668 is a critical-severity flaw (CVSS 9.8) affecting bitlbee, bitlbee-libpurple. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

bitlbee-libpurple before 3.5.1 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. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-10189.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance3.0% (top 13%)
CISA exploited listNo
WeaknessCWE-476
Published2017-03-14
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: bitlbee

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

bitlbee bitlbee UPGRADE
Affected: <= 3.4.2
Fixed in: newer than 3.4.2
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy bitlbee || rpm -q bitlbee || bitlbee --version
2. UPGRADE to newer than 3.4.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade bitlbee
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade bitlbee
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
bitlbee bitlbee-libpurple UPGRADE
Affected: <= 3.5
Fixed in: newer than 3.5
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy bitlbee-libpurple || rpm -q bitlbee-libpurple || bitlbee-libpurple --version
2. UPGRADE to newer than 3.5 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade bitlbee-libpurple
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade bitlbee-libpurple
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-5668?

bitlbee: upgrade to newer than 3.4.2; bitlbee-libpurple: upgrade to newer than 3.5. Exact commands for each OS are on this page.

Is CVE-2017-5668 being exploited?

CVE-2017-5668 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-5668 affect?

CVE-2017-5668 affects bitlbee, bitlbee-libpurple. Severity is critical (CVSS 9.8). bitlbee-libpurple before 3.5.1 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. NOTE: t

How urgent is CVE-2017-5668?

Priority 61/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.