Ubuntu USN-8832-1 Fixes Booth Vulnerability
Tech GuruQuick Answer
USN-8832-1 fixes a Booth message-authentication flaw that could let a remote attacker bypass authentication. Updating the package is not the final step: Ubuntu explicitly requires restarting Booth. Coordinate that restart with the cluster operator and verify ticket state afterward.
Confirm Scope And Apply The Supported Fix
What to do now: identify the Booth sites and arbitrators using the affected Ubuntu packages, confirm the matching ESM Apps update is available, and plan a controlled restart. Do not restart every cluster participant blindly or treat a successful package transaction as proof that the running service is fixed.
Last verified: October 2, 2026 UTC against Ubuntu's notice. No cluster operation or security test was performed.
Scope And Authority
| Product scope | Booth vulnerability on Ubuntu 24.04 LTS (noble), Ubuntu 22.04 LTS (jammy), Ubuntu 20.04 ESM (focal), Ubuntu 18.04 ESM (bionic) |
|---|---|
| Advisory | USN-8832-1 |
| CVE | CVE-2024-3049 |
| Authoritative release date | 2026-09-28 14:20:51.408419 UTC |
| Authority revision date | No separate material revision date is stated by Ubuntu; verified against the first-party notice API. |
| Affected versions | The Ubuntu releases and source packages enumerated in USN-8832-1: Ubuntu 24.04 LTS (noble), Ubuntu 22.04 LTS (jammy), Ubuntu 20.04 ESM (focal), Ubuntu 18.04 ESM (bionic). |
| Fixed version | bionic: booth 1.0-6ubuntu1+esm1 / focal: booth 1.0-174-gce9f821-1ubuntu0.2+esm1 / jammy: booth 1.0-237-gdd88847-4ubuntu2.2+esm1 / noble: booth 1.1-1ubuntu4+esm1 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
Booth could allow unintended access to network services. After a standard system update you need to restart Booth to make all the necessary changes.
What To Validate Now
- Map the cluster. Record the Ubuntu release, installed
boothpackage, site/arbitrator role and current ticket state. - Match the update. Use the listed fixed version for that release or a supported superseding update. Install the binary package from the approved Ubuntu channel, not a source archive.
- Activate and test. Follow the cluster maintenance procedure to restart Booth, then verify communication, ticket ownership and dependent resources. Stop rollout if ticket state differs from the approved baseline.
- Keep the result. Retain before/after package versions, restart timestamps, Booth logs and cluster validation. If recovery requires an older vulnerable build, isolate and escalate rather than call it remediated.
Operational Cautions
Some listed fixes are delivered through Ubuntu Pro or ESM. Confirm entitlement and repository state before the change, use the exact supported release stream, and test dependent services, clusters, and rollback. Severity alone is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
