On this page (7 sections)

Ubuntu has published USN-9144-1, a security notice for ngIRCd, a lightweight Internet Relay Chat (IRC) server. According to Ubuntu, the server can be made to crash if it receives specially crafted network traffic, which results in a denial of service.

If you run ngIRCd on Ubuntu 16.04 LTS, 18.04 LTS or 20.04 LTS, this notice is relevant to you. For 20.04 and 18.04, Ubuntu says the fix is available through Ubuntu Pro via ESM Apps rather than as a plain standard update.

What Ubuntu says happened

The notice states that ngIRCd incorrectly handled SERVER commands that arrive without a prefix, leading to an out-of-bounds read. Ubuntu says a remote attacker could possibly use this to cause ngIRCd to crash, resulting in a denial of service.

The notice does not describe data theft, code execution or any confirmed attacks in the wild, and it gives no severity score. Treat it as an availability problem unless further information appears. This is the only source in our research, so details beyond the Ubuntu notice are unconfirmed.

The weakness in plain terms

As general background (not a detail from the notice), an out-of-bounds read happens when a program reads memory past the end of the data it was given. Such reads can make a process misbehave, and Ubuntu's assessment here is that the result could be a crash of ngIRCd.

For a chat server, a crash would typically mean connected users lose their sessions until the service is running again. How quickly that happens depends on whether you have something that restarts the service automatically, which is worth checking on your own systems.

Who is realistically exposed

  • Anyone running ngIRCd as a package on Ubuntu 20.04, 18.04 or 16.04.
  • Servers where the IRC port is reachable from the internet or from untrusted networks, since the notice describes a remote attacker.
  • Teams that host community, project or internal chat on ngIRCd and depend on it staying up.

If your server only listens on a private network or behind a VPN, the practical exposure is smaller, but it is still worth patching.

How to check your exposure

The first command lists the installed ngircd package and its version on Debian and Ubuntu. Compare the result with the fixed versions in the table below. A version matching or newer than the one listed for your release means the fix is installed.

Show the installed ngircd package version (Debian/Ubuntu)Shell
dpkg -l ngircd
Fixed ngircd package versions from USN-9144-1
Ubuntu releaseFixed versionHow to get it
20.04 LTS (focal)25-3ubuntu0.1~esm1Ubuntu Pro, ESM Apps
18.04 LTS (bionic)24-2ubuntu0.1~esm1Ubuntu Pro, ESM Apps
16.04 LTS (xenial)22.1-2ubuntu0.1~esm1Not specified in the notice text we reviewed

The next command checks whether ngIRCd is listening and on which addresses. The default IRC port is 6667, but your configuration may differ. Look for whether it is bound to a public address or only to localhost or a private interface.

List listening sockets and filter for ngircd (run as root)Shell
ss -tlnp | grep ngircd

What to do now

  1. Run the dpkg check above on every host that might run ngIRCd, including old or forgotten servers.
  2. If you are on 20.04 or 18.04, attach the machine to Ubuntu Pro. Ubuntu says it is free for up to five machines and the fix comes through ESM Apps.
  3. On 16.04, check the Ubuntu notice and your update sources for how the 22.1-2ubuntu0.1~esm1 package is delivered.
  4. Apply the standard system update to install the fixed ngircd package.
  5. Restart ngIRCd after the update, as Ubuntu instructs, so the new code is actually running.
  6. Re-run dpkg -l ngircd and confirm the version matches the table.
  7. If you cannot patch immediately, restrict access to the IRC and server-linking ports with firewall rules so only trusted peers and users can connect.
  8. Plan an upgrade away from releases that need ESM for fixes.

The command below upgrades only the ngircd package on Debian-based systems. Run it as root or with sudo, after the machine has access to the fixed package. It should report ngircd being upgraded to the version in the table.

Update only the ngircd package (Debian/Ubuntu, fixed packages require Ubuntu Pro ESM on 20.04 and…Shell
sudo apt update && sudo apt install --only-upgrade ngircd
Caution. Restarting ngIRCd disconnects all connected users and drops links to other IRC servers. Do it in a quiet period.

This command restarts the service so the updated package is the one running. Run it with sudo on systemd-based hosts.

Restart the ngIRCd service after updating (systemd)Shell
sudo systemctl restart ngircd
Ubuntu says a community fix for 20.04 and 18.04 might become publicly available in the future. Do not wait for it if the server is internet-facing.

Detection and monitoring afterwards

Because the impact is a crash, the most useful signal is availability. Watch for unexpected ngIRCd restarts or exits in the system journal, and for connections to the server port from addresses you do not recognize. Set up an external check on the IRC port so you learn about an outage before your users do; see our guide to uptime monitoring or Webforta Monitor for this kind of check.

This command shows the last seven days of ngircd service logs on systemd hosts. Look for unexpected exits or restarts.

Review recent ngircd log entries for crashes or restarts (systemd)Shell
journalctl -u ngircd --since "7 days ago"

If you find repeated crashes that line up with unfamiliar remote addresses, restrict those sources at the firewall and keep the logs. For hosts that also serve websites, our small business website security guide covers wider hardening, and more advisory coverage is in the Webforta blog.

Timeline

  • 17 November 2026: Ubuntu publishes USN-9144-1 for ngIRCd, referencing CVE-2020-14148.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. USN-9144-1: ngIRCd vulnerability | Ubuntu security notices | Ubuntuubuntu.com ·
  • ngIRCd
  • Ubuntu
  • USN
  • denial of service
  • CVE-2020-14148