On this page (7 sections)
Ubuntu has published security notice USN-9077-1 for MiniSSDPd, a small daemon that keeps memory of UPnP devices that announced themselves. According to Ubuntu, the program mishandles device updates in some circumstances, which causes a use-after-free and can let a remote attacker crash the service.
The notice covers Ubuntu 18.04 LTS only, and the fixed package is delivered through Ubuntu Pro (ESM Apps). If you run an older 18.04 server or appliance that has minissdpd installed, this is worth a quick check. Only one source covers this story so far, and it is the Ubuntu notice itself.
What Ubuntu says happened
Ubuntu's description is short. MiniSSDPd incorrectly handled device updates under certain circumstances, leading to a use-after-free. A remote attacker could possibly use this to make MiniSSDPd crash, resulting in a denial of service. The overview line says the daemon could be made to crash if it received specially crafted network traffic.
The notice does not report code execution, data exposure or active exploitation, and it does not give a severity rating. The research includes no NVD or CISA record for the CVE, so this article does not state a CVSS score. Treat the issue as an availability problem unless further analysis says otherwise.
The weakness in plain terms
A use-after-free happens when a program releases a piece of memory and then keeps using it. The result is usually unpredictable behavior, and in the mildest case the process simply crashes. Here, Ubuntu describes the outcome as a crash of the MiniSSDPd service leading to denial of service.
The trigger is network traffic, so the practical question is whether the daemon is reachable by anyone you do not trust. The notice does not say which networks or interfaces are exposed by default, so check your own configuration rather than assuming.
Who is realistically exposed
- Servers, desktops or appliances on Ubuntu 18.04 LTS (bionic) that have the minissdpd package installed.
- Hosts where the daemon can receive traffic from untrusted networks, which raises the chance of a remote crash. This is general reasoning, not something the notice states.
- Systems without Ubuntu Pro: the notice lists the fix under ESM Apps and says a community fix might become publicly available in the future.
Ubuntu lists only 18.04 LTS in this notice. The research does not say whether other releases are affected, so do not read the absence of other releases as proof that they are safe.
How to check your exposure
This read-only command lists the installed minissdpd package and its version on Ubuntu. If it prints a version, the package is installed; compare it with 1.5.20180223-1ubuntu0.1~esm1.
dpkg -l minissdpdThis read-only command shows whether a minissdpd process is currently running. No output means it is not running right now.
ps aux | grep [m]inissdpdWhat to do now
- Run the dpkg check above on every Ubuntu 18.04 host you manage and note where minissdpd is installed.
- If the package is not needed, consider removing it through your normal change process so the exposure disappears.
- If you use Ubuntu Pro, attach the machine and run a standard system update so the ESM Apps fix, version 1.5.20180223-1ubuntu0.1~esm1, is installed.
- After the update, restart MiniSSDPd as the notice instructs, since a standard update alone does not apply all changes.
- Re-run the version check to confirm the fixed version is in place.
- If you cannot use Ubuntu Pro, restrict who can send traffic to the host with your firewall and plan a move off 18.04.
This standard command refreshes package lists and upgrades only the minissdpd package on a system that already has access to the ESM Apps repository. Look for the fixed version in the output.
sudo apt update && sudo apt install --only-upgrade minissdpdUbuntu instructs you to restart MiniSSDPd after the update. The notice does not give the service name, so first confirm it on your host. This read-only command lists service units matching the name; note the exact unit name it prints.
systemctl list-units --all | grep -i minissdpdThen restart the unit you found. The example below assumes the unit is called minissdpd; replace it if your output shows a different name. It should return without errors.
sudo systemctl restart minissdpdMonitoring and hardening afterwards
Because the impact is a crash, watch for unexpected service exits. Check your system logs and service status for repeated minissdpd restarts or failures, and alert on them if the daemon matters to your setup. Keep UPnP and device discovery services off networks they do not need to reach, and block them at the network edge where possible. General guidance on keeping servers and sites in good shape is in our small business website security guide.
If you run public websites on these hosts, uptime monitoring can tell you when a server becomes unreachable for any reason, including a crashed service. We also covered other recent Ubuntu 18.04 notices: USN-9078-1 for ncmpc and USN-9063-1 for Yodl.
What is still unknown
- No severity rating or CVSS score is provided in the research.
- No exploitation in the wild is reported, but the research also does not confirm the absence of it.
- The notice does not say which network interfaces or default configurations expose the flaw.
- Only the Ubuntu notice covers the story so far; no independent analysis is available.
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.
