openSUSE Tumbleweed — npm20 — multiple vulnerabilities (20 CVEs) — patch and remediation guide

📖 ~4 min read  •  Source: SUSE advisory SUSE-SU-2024:1301-1 (see also SUSE bugzilla)

Related CVEs: CVE-2024-27983 CVE-2024-21890 CVE-2024-21891 CVE-2024-21892 CVE-2024-21896 CVE-2024-22017 CVE-2024-22019 CVE-2023-39331  +12 more

Upstream summary: An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.

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

npm20 on openSUSE Tumbleweed runs only when something invokes it, so there is no crash loop and no failed unit to notice — the exposure is input-driven. A developer build, a CI job, a package rebuild or triage tooling that runs objdump, readelf or gdb across an untrusted binary can hit a malformed section header and corrupt memory inside the toolchain process, running code as the build user. On a shared builder or CI runner that means tampered build output rather than downtime. npm20 is a build-time developer tool that exits when the command finishes, so there is no unit to restart — only in-flight builds and long-lived helpers such as distcc or clangd still hold the old binaries.

Environment & Reproduction

Reproduction targets openSUSE Tumbleweed. Confirm release and installed package:

cat /etc/os-release
rpm -q npm20
zypper info npm20 | head -20
zypper lr -E                              # enabled repositories

Exercise the workload that uses npm20 while collecting:

rpm -qa --qf '%{VENDOR}\t%{BUILDHOST}\t%{BUILDTIME:date}\t%{NAME}-%{VERSION}-%{RELEASE}\n' | awk -F'\t' '$1 !~ /SUSE/'  # packages NOT built by SUSE are your own builds - these were compiled with the vulnerable npm20 and need rebuilding
readelf -p .comment /usr/local/bin/YOURAPP  # prints e.g. 'GCC: (SUSE Linux) 7.5.0' - the compiler that actually built it (binutils; empty output just means the section was stripped)
objdump -s -j .comment /usr/local/bin/YOURAPP  # the same evidence via objdump (binutils)
sudo journalctl -xe --no-pager | tail -200
sudo tail -200 /var/log/zypp/history
sudo journalctl -k | grep -i apparmor | tail -100
# Bundle evidence for SUSE / community support:
sudo supportconfig -R /var/tmp -B npm20

Root Cause Analysis

Root cause is documented in SUSE advisory SUSE-SU-2024:1301-1. openSUSE security maintainers shipped fixes in the corresponding npm20 update for openSUSE Tumbleweed; running an outdated build leaves the host exposed to the failure modes described in the advisory. Correlate zypper history with system logs:

sudo zypper history | grep npm20
sudo zypper history --since='-7 days' | tail -40
sudo journalctl -k | grep -i apparmor | tail -100
cat /proc/sys/kernel/tainted   # non-zero = tainted kernel / out-of-tree modules
snapper list | tail -20         # snapshots taken around each zypper transaction

Quick Triage

Run these on openSUSE Tumbleweed to capture the current state of npm20:

rpm -q npm20                              # installed NVR
rpm -V npm20                              # verify shipped files
sudo zypper ref                            # refresh repos
sudo zypper dup --dry-run                  # pending rolling updates
systemctl --failed --no-pager
sudo firewall-cmd --list-all
sudo aa-status                             # AppArmor profiles
rpm -ql npm20 | grep -E '^/(usr/lib|etc)/systemd/(system|user)/[^/]+\.(service|socket|timer|path|target|mount)$'  # the units npm20 REALLY ships - NO OUTPUT means it ships no service at all, so never run systemctl on it
rpm -ql npm20 | grep -E '^/usr/sbin/rc[^/]+$'  # SUSE-only rcNAME compat symlink (it points at /usr/sbin/service, not at a unit): the NAME after 'rc' IS the service name - bind ships /usr/sbin/rcnamed, so the unit is named.service

Step-by-Step Diagnosis

1. List failed systemd units.

   systemctl --failed --no-pager

2. Tail the journal for npm20 and the system bus.

   sudo journalctl -xe -f --no-pager

3. Inspect firewall posture (firewalld is the default on openSUSE).

   sudo firewall-cmd --list-all-zones --permanent
   sudo nft list ruleset 2>/dev/null | head -50

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

   sudo journalctl -k | grep -i 'apparmor="DENIED"' | tail -30
   sudo aa-status

5. Verify npm20 integrity and reinstall if anything is altered.

   sudo rpm -V npm20
   sudo zypper verify
   sudo zypper install --force npm20

6. Inspect Snapper snapshots to know exactly which transaction introduced the regression.

   sudo snapper list | tail -20
   sudo snapper status <pre-id>..<post-id>

7. Correlate findings with /var/log/zypp/history, zypper history, and SUSE advisory SUSE-SU-2024:1301-1 to pin the change that introduced the regression.

Solution – Primary Fix

Apply the corrective zypper transaction referenced by SUSE advisory SUSE-SU-2024:1301-1, then reload affected systemd units:

sudo zypper ref                                      # refresh repos
# Tumbleweed is a rolling release — use 'dup', not 'patch':
sudo zypper dup --no-allow-vendor-change             # rolling distribution upgrade
# To target only the affected package while still on rolling:
sudo zypper dup --no-allow-vendor-change npm20
# Unit name may differ from pkg name; check first:
rpm -q npm20                                          # confirm new NVR

For kernel / glibc / systemd / openssl rolls a reboot is required. Tumbleweed does not ship Live Patching, so plan a maintenance window or use Snapper to roll back if a regression appears:

sudo zypper ps -s                      # services using deleted libs
sudo snapper list | tail -5            # confirm pre/post snapshots exist
sudo systemctl reboot                  # or: sudo shutdown -r now

Solution – Alternative Approaches

If the primary fix is not viable, choose from these:

• Roll back via Snapper (Btrfs snapshots are taken automatically before zypper transactions on openSUSE Tumbleweed). This is the primary safety net for openSUSE administrators:

  sudo snapper list
  sudo snapper status <pre-id>..<post-id>   # diff between two snapshot numbers
  sudo snapper undochange <pre-id>..<post-id>
  sudo snapper rollback <pre-id>            # boot the host into the chosen snapshot
  sudo systemctl reboot

• Lock the package so zypper cannot upgrade it:

  sudo zypper al npm20                   # add lock
  zypper ll | grep npm20                 # list locks
  sudo zypper rl npm20                   # remove lock

• Install an older NVR if a regression is suspected:

  zypper se -s npm20                     # show all available versions
  sudo zypper install --oldpackage npm20-<older-NVR>

• Disable the AppArmor profile briefly to confirm policy is the cause, then re-enable:

  # reproduce, capture denials in the journal:
  sudo journalctl -k | grep apparmor | tail

• Pin Tumbleweed to a known-good snapshot from the openSUSE history server while you investigate. This keeps the rolling release reproducible across a fleet:

  # Edit /etc/zypp/repos.d/repo-oss.repo and point baseurl at
  #   http://download.opensuse.org/history/<YYYYMMDD>/tumbleweed/repo/oss/
  sudo zypper ref
  sudo zypper dup --no-allow-vendor-change

Verification & Acceptance Criteria

All of these should pass after the fix:

rpm -q npm20                                            # expected fixed NVR
sudo zypper dup --dry-run                                # no pending rolls expected
sudo firewall-cmd --list-services
sudo aa-status | head -5
sudo zypper ps -s                                        # any services still using deleted libs

The conditions described in the advisory must no longer be reported for npm20 across two consecutive runs.

Rollback Plan

Capture state before any change. On openSUSE, Snapper is the canonical rollback path:

rpm -qa > /root/rpm-pre.txt
sudo zypper history list > /root/zypper-history-pre.txt
# Snapper takes pre/post snapshots automatically on Btrfs root.
sudo snapper create -d 'pre-patch-npm20'   # explicit named snapshot
sudo snapper list | head

To revert if the patch / roll is bad:

# Preferred on Btrfs root — boot the prior snapshot:
sudo snapper list
sudo snapper rollback <pre-id>
sudo systemctl reboot
# Or downgrade just the package:
sudo zypper install --oldpackage npm20-<older-NVR>
# Custom AppArmor profile cleanup:

Prevention & Hardening

Reduce the chance of this recurring on openSUSE Tumbleweed:

• Run rolling upgrades on a schedule — Tumbleweed receives a snapshot most weekdays. Stagger across the fleet so any regression is caught early:

  sudo zypper ref
  sudo zypper dup --no-allow-vendor-change
  # Optional: drive from salt/ansible with a maintenance window per host group.

• Subscribe to opensuse-security-announce and watch suse.com/support/update.

• Lock sensitive packages so they cannot be auto-upgraded:

  sudo zypper al npm20

• Ensure Snapper is enabled on the root subvolume and pre/post hooks run for every zypper transaction. This is the cornerstone of safe openSUSE patching:

  sudo snapper -c root get-config | head
  # Default zypper plugin: /usr/lib/zypp/plugins/commit/snapper.zypp-commit-plugin
  sudo snapper list | tail -10

• Monitor file integrity with AIDE:

  sudo zypper install -y aide
  sudo aide --init && sudo mv /var/lib/aide/aide.db.new /var/lib/aide/aide.db
  sudo aide --check

• Keep AppArmor profiles in enforce; review /etc/apparmor.d/ after every package upgrade.

• Apply CIS / openSUSE hardening guidance and use salt or ansible to enforce baseline state across the fleet.

Related Errors & Cross-Refs

Issues that commonly surface alongside a npm20 update: zypper lock contention, systemd unit ordering cycles, AppArmor denials, firewalld zone drift, and kernel taint flags. Useful triage:

sudo zypper ps -s
systemd-analyze critical-chain
sudo journalctl -k | grep apparmor | tail
sudo firewall-cmd --get-active-zones
cat /proc/sys/kernel/tainted
sudo snapper list | tail

View all opensuse-tumbleweed tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Primary reference: SUSE advisory SUSE-SU-2024:1301-1 (see also SUSE bugzilla). Manual pages useful on openSUSE Tumbleweed:

man zypper
man zypper.conf
man systemctl
man journalctl
man firewall-cmd
man snapper
man apparmor
man aa-status

Other resources: openSUSE documentation, suse.com/security, openSUSE security portal, and per-package notes in /usr/share/doc/packages/npm20/ for components implicated in this advisory.

View all openSUSE Tumbleweed tutorials on the Tutorials Hub →