Ubuntu 22.04 — golang-1.13 — multiple vulnerabilities (19 CVEs) — patch and remediation guide

📖 ~4 min read  •  Source: Ubuntu Security Notice USN-6038-2

Related CVEs: CVE-2022-1705 CVE-2022-27664 CVE-2022-28131 CVE-2022-2879 CVE-2022-2880 CVE-2022-29526 CVE-2022-30629 CVE-2022-30630  +11 more

Upstream summary: USN-6038-1 fixed several vulnerabilities in Go 1.18. This update provides
the corresponding updates for Go 1.13 and Go 1.16.

CVE-2022-29526 and CVE-2022-30630 only affected Go 1.16.

Original advisory details:

It was discovered that the Go net/http module incorrectly handled
Transfer-Encoding headers in the HTTP/1 client. A remote attacker could
possibly use this issue to perform an HTTP Request Smuggling attack.
(CVE-2022-1705)

It was discovered that Go did not prop

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

On Ubuntu 22.04 (jammy) hosts that have golang-1.13 installed, administrators report behaviour consistent with Ubuntu Security Notice USN-6038-2: apt reports pending security updates, services backed by golang-1.13 fail or restart unexpectedly, AppArmor denials appear in the kernel log, and — for security-rated advisories — the host is exposed to the vulnerability set above. Impact ranges from a single service-restart loop to wider availability incidents whenever golang-1.13 sits on the serving path.

Environment & Reproduction

Reproduction targets Ubuntu 22.04 (jammy). Confirm release and installed package:

lsb_release -a
cat /etc/os-release
dpkg -l golang-1.13 | tail -2
apt-cache policy golang-1.13
uname -r

Trigger the workflow that exposes golang-1.13 — multiple vulnerabilities (19 CVEs) — patch and remediation guide while collecting:

sudo journalctl -u golang-1.13 -b --no-pager | tail -200
sudo journalctl -xe --no-pager | tail -200
sudo tail -200 /var/log/apt/history.log
sudo tail -200 /var/log/kern.log | grep -i apparmor

Root Cause Analysis

Root cause is documented in Ubuntu Security Notice USN-6038-2. Canonical security maintainers shipped fixes in the corresponding golang-1.13 update for Ubuntu 22.04; running an outdated build leaves the host exposed to the failure modes described in the advisory. Fixes land in the jammy-security pocket of the main archive. Correlate apt history with the journal:

grep -A2 -B2 golang-1.13 /var/log/apt/history.log
zgrep -A2 -B2 golang-1.13 /var/log/apt/history.log.*.gz 2>/dev/null
cat /proc/sys/kernel/tainted   # non-zero = tainted kernel / out-of-tree modules

Quick Triage

Run these on Ubuntu 22.04 to capture the current state of golang-1.13:

dpkg -l golang-1.13 | tail -1                  # installed version
dpkg -V golang-1.13                             # verify shipped files
sudo apt update && apt list --upgradable 2>/dev/null | grep -i security
systemctl is-active golang-1.13
sudo ufw status verbose 2>/dev/null | head -20
sudo aa-status 2>/dev/null | head -20
# If golang-1.13 ships a service unit (unit/job name often differs from pkg name, e.g.
# bind9→named, apache2→apache2, postgresql-NN→postgresql@NN-main):
systemctl list-unit-files | grep -i golang | head

Step-by-Step Diagnosis

1. List failing services.

   systemctl --failed --no-pager

2. Tail the journal / syslog for golang-1.13.

   sudo journalctl -u golang-1.13 -f --no-pager
   sudo journalctl -xe -f --no-pager

3. Inspect UFW (Uncomplicated Firewall) state.

   sudo ufw status numbered
   sudo ufw show added
   sudo iptables -L -n -v | head -30

4. Surface AppArmor denials and switch the profile to complain mode if needed.

   sudo journalctl -k 2>/dev/null | grep -i 'apparmor="DENIED"' | tail -30
   sudo aa-status
   # /etc/apparmor.d/usr.bin.golang-1.13 or usr.sbin.golang-1.13 — inspect first
   sudo aa-complain /etc/apparmor.d/usr.bin.golang-1.13 2>/dev/null || true

5. Verify golang-1.13 integrity and reinstall if anything is altered.

   sudo dpkg -V golang-1.13
   sudo debsums -c golang-1.13 2>/dev/null
   sudo apt install --reinstall -y golang-1.13

6. Correlate findings with /var/log/apt/history.log, /var/log/dpkg.log, and Ubuntu Security Notice USN-6038-2 to pin the change that introduced golang-1.13 — multiple vulnerabilities (19 CVEs) — patch and remediation guide.

Solution – Primary Fix

Apply the corrective apt transaction referenced by Ubuntu Security Notice USN-6038-2, then reload the affected service:

sudo apt update
sudo apt -y install --only-upgrade golang-1.13
sudo systemctl daemon-reload
# Service name may differ from pkg name; check first:
systemctl list-unit-files | grep -i golang | head
sudo systemctl restart golang-1.13
dpkg -l golang-1.13 | tail -1            # confirm new version
systemctl is-active golang-1.13

For kernel / glibc / systemd / openssl advisories a reboot (or Livepatch) is required:

sudo apt install -y needrestart
sudo needrestart -r l       # list units that need restart
sudo systemctl reboot       # or: sudo shutdown -r now
# Livepatch (Ubuntu Pro) avoids reboot for many kernel CVEs:
sudo canonical-livepatch status
sudo canonical-livepatch refresh

Solution – Alternative Approaches

If the primary upgrade is not viable, pick from these:

• Hold the package so apt cannot upgrade it:

  sudo apt-mark hold golang-1.13
  apt-mark showhold | grep golang-1.13
  # Release the hold later with:
  sudo apt-mark unhold golang-1.13

• Pin a known-good version via apt preferences:

  # /etc/apt/preferences.d/golang-1.13.pref
  Package: golang-1.13
  Pin: version <good-version>
  Pin-Priority: 1001

• Downgrade to an older version if a regression is suspected:

  apt-cache madison golang-1.13
  sudo apt install --allow-downgrades -y golang-1.13=<older-version>

• Investigate AppArmor blocking the new binary; switch to complain briefly, capture denials, then re-enforce:

  sudo aa-complain /etc/apparmor.d/usr.bin.golang-1.13 2>/dev/null
  # reproduce the failure
  sudo journalctl -k | grep apparmor | tail
  sudo aa-enforce /etc/apparmor.d/usr.bin.golang-1.13 2>/dev/null

• Apply Canonical Livepatch (Ubuntu Pro) to land kernel fixes without reboot:

  sudo canonical-livepatch status
  sudo canonical-livepatch refresh

• Take only the security pocket update and defer the full point-release upgrade:

  sudo apt -y install --only-upgrade -t jammy-security golang-1.13

Verification & Acceptance Criteria

All of these should pass after the fix is applied:

dpkg -l golang-1.13 | tail -1                                  # expected fixed version
apt list --upgradable 2>/dev/null | grep -i security || echo OK
systemctl is-active golang-1.13
sudo journalctl -u golang-1.13 --since "5 minutes ago" --no-pager | grep -iE "error|fail" || echo OK
sudo ufw status numbered | head
sudo aa-status 2>/dev/null | head -5

The original reproduction for golang-1.13 — multiple vulnerabilities (19 CVEs) — patch and remediation guide must not trigger across two consecutive runs.

Rollback Plan

Capture state before any change:

apt list --installed 2>/dev/null > /root/apt-pre.txt
dpkg --get-selections > /root/dpkg-pre.txt
# ZFS-on-root (Ubuntu 20.04+ default installer option):
sudo zfs snapshot rpool/ROOT/ubuntu@pre-golang-1-13
# LVM-on-root:
sudo lvcreate -L 4G -s -n root_pre_patch /dev/<vg>/<root-lv>

To revert:

sudo apt install --allow-downgrades -y golang-1.13=<old-version>
sudo systemctl daemon-reload
sudo systemctl restart golang-1.13
# Kernel rollback: pick the prior kernel from the GRUB menu, then:
sudo systemctl reboot
# ZFS rollback (rolls the whole root dataset):
sudo zfs rollback -r rpool/ROOT/ubuntu@pre-golang-1-13

Prevention & Hardening

Reduce the chance of this recurring on Ubuntu 22.04 (jammy):

• Enable scheduled security updates via unattended-upgrades:

  sudo apt install -y unattended-upgrades update-notifier-common
  sudo dpkg-reconfigure -plow unattended-upgrades
  # /etc/apt/apt.conf.d/50unattended-upgrades:
  Unattended-Upgrade::Allowed-Origins { "${distro_id}:${distro_codename}-security"; };

• Install needrestart so services restart automatically after library upgrades:

  sudo apt install -y needrestart
  # /etc/needrestart/needrestart.conf -> $nrconf{restart} = 'a';

• Attach Ubuntu Pro to enable Livepatch and extended security coverage:

  sudo pro attach <token>
  sudo pro enable livepatch

• Subscribe to ubuntu-security-announce and watch ubuntu.com/security/cves.

• Monitor file integrity with debsums and AIDE:

  sudo apt install -y debsums aide
  sudo debsums -ca
  sudo aideinit && sudo mv /var/lib/aide/aide.db.new /var/lib/aide/aide.db
  sudo aide --check

• For estate-wide patching, manage with Canonical Landscape:

  sudo apt install -y landscape-client
  sudo landscape-config

• Keep AppArmor profiles in enforce mode and apply CIS Ubuntu Linux Benchmark hardening.

Related Errors & Cross-Refs

Issues that commonly surface alongside golang-1.13 — multiple vulnerabilities (19 CVEs) — patch and remediation guide: apt lock contention, broken dpkg state, systemd ordering cycles, AppArmor denials, and UFW rule drift. Useful triage:

sudo dpkg --configure -a
sudo apt --fix-broken install
systemd-analyze critical-chain
sudo journalctl -k 2>/dev/null | grep -i apparmor | tail
cat /proc/sys/kernel/tainted

View all ubuntu-22-04 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Primary reference: Ubuntu Security Notice USN-6038-2. Manual pages useful on Ubuntu 22.04:

man apt
man apt-get
man apt-mark
man dpkg
man systemctl
man journalctl
man ufw
man apparmor
man aa-status
man unattended-upgrades
man canonical-livepatch
man pro

Other resources: Ubuntu Security Notices, Ubuntu CVE Tracker, Ubuntu upgrade notes, and per-package notes in /usr/share/doc/golang-1.13/ for components implicated in golang-1.13 — multiple vulnerabilities (19 CVEs) — patch and remediation guide.