openSUSE Leap 15.6 — python312-pip — vulnerability — patch and remediation guide

📖 ~4 min read  •  Source: SUSE advisory SUSE-CU-2023:4334-1 (see also SUSE bugzilla)

Related CVEs: CVE-2023-5752

Upstream summary: When installing a package from a Mercurial VCS URL (ie "pip install hg+…") with pip prior to v23.3, the specified Mercurial revision could be used to inject arbitrary configuration options to the "hg clone" call (ie "–config"). Controlling the Mercurial configuration can modify how and which repository is installed. This vulnerability does not affect users who aren't installing from Mercurial.

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 openSUSE Leap 15.6 hosts that have python312-pip installed, administrators report behaviour consistent with SUSE advisory SUSE-CU-2023:4334-1: zypper patch-check lists open patches, services backed by python312-pip fail or restart unexpectedly, AppArmor profile warnings appear in journalctl -k — 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 python312-pip sits on the serving path.

Environment & Reproduction

Reproduction targets openSUSE Leap 15.6. Confirm release and installed package:

cat /etc/os-release
rpm -q python312-pip
zypper info python312-pip | head -20
zypper lr -E                              # enabled repositories
SUSEConnect --status-text 2>/dev/null || echo 'SCC not connected (optional on openSUSE Leap)'

Trigger the workflow that exposes python312-pip — vulnerability — patch and remediation guide while collecting:

sudo journalctl -u python312-pip -b --no-pager | tail -200
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 python312-pip

Root Cause Analysis

Root cause is documented in SUSE advisory SUSE-CU-2023:4334-1. openSUSE security maintainers shipped fixes in the corresponding python312-pip update for openSUSE Leap 15.6; 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 python312-pip
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

Quick Triage

Run these on openSUSE Leap 15.6 to capture the current state of python312-pip:

rpm -q python312-pip                              # installed NVR
rpm -V python312-pip                              # verify shipped files
sudo zypper patch-check                    # open patches
sudo zypper lp 2>/dev/null | head
systemctl --failed --no-pager
sudo firewall-cmd --list-all
sudo aa-status                             # AppArmor profiles
# If python312-pip ships a systemd unit (unit name may differ from pkg name, e.g.
# bind→named, postgresql-server→postgresql, php-fpm→php-fpm):
systemctl list-unit-files | grep -i python312 | head

Step-by-Step Diagnosis

1. List failed systemd units.

   systemctl --failed --no-pager

2. Tail the journal for python312-pip and the system bus.

   sudo journalctl -u python312-pip -f --no-pager
   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
   sudo aa-complain /etc/apparmor.d/usr.sbin.python312-pip 2>/dev/null || true

5. Verify python312-pip integrity and reinstall if anything is altered.

   sudo rpm -V python312-pip
   sudo zypper verify
   sudo zypper install --force python312-pip

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-CU-2023:4334-1 to pin the change that introduced python312-pip — vulnerability — patch and remediation guide.

Solution – Primary Fix

Apply the corrective zypper transaction referenced by SUSE advisory SUSE-CU-2023:4334-1, then reload affected systemd units:

sudo zypper ref                        # refresh repos
sudo zypper -n patch                   # apply ALL open patches (recommended)
# Or target a single package:
sudo zypper -n update python312-pip
sudo systemctl daemon-reload
# Unit name may differ from pkg name; check first:
systemctl list-unit-files | grep -i python312 | head
sudo systemctl restart python312-pip
rpm -q python312-pip                           # confirm new NVR
systemctl is-active python312-pip 2>/dev/null  # confirm running (if a unit exists)

For kernel / glibc / systemd / openssl advisories a reboot is required. Snapper takes pre/post snapshots on Btrfs root automatically, giving a safety net:

sudo zypper ps -s                      # services using deleted libs
sudo snapper list | tail -5            # pre/post snapshots around the patch
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 Leap 15.6). 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 python312-pip                   # add lock
  zypper ll | grep python312-pip                 # list locks
  sudo zypper rl python312-pip                   # remove lock

• Install an older NVR if a regression is suspected:

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

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

  sudo aa-disable /etc/apparmor.d/usr.sbin.python312-pip
  # reproduce, capture denials in the journal:
  sudo journalctl -k | grep apparmor | tail
  sudo aa-enforce /etc/apparmor.d/usr.sbin.python312-pip

• openSUSE Leap follows the SUSE Linux Enterprise patch stream. Sync against the official update repository if a mirror has drifted:

  sudo zypper mr -e repo-update          # ensure update repo is enabled
  sudo zypper ref repo-update
  sudo zypper -n patch

Verification & Acceptance Criteria

All of these should pass after the fix:

rpm -q python312-pip                                            # expected fixed NVR
sudo zypper patch-check                                  # 0 critical patches outstanding
systemctl is-active python312-pip 2>/dev/null
sudo journalctl -u python312-pip --since "5 minutes ago" --no-pager | grep -iE "error|fail" || echo OK
sudo firewall-cmd --list-services
sudo aa-status | head -5
sudo zypper ps -s                                        # any services still using deleted libs

The original reproduction for python312-pip — vulnerability — patch and remediation guide must not trigger 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-python312-pip'   # 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 python312-pip-<older-NVR>
sudo systemctl daemon-reload
sudo systemctl restart python312-pip
# Custom AppArmor profile cleanup:
sudo apparmor_parser -R /etc/apparmor.d/usr.sbin.python312-pip

Prevention & Hardening

Reduce the chance of this recurring on openSUSE Leap 15.6:

• Enable automatic patch installation:

  sudo zypper install -y zypper-automatic
  sudo systemctl enable --now zypper-automatic.timer
  # Or use YaST: yast2 online_update_configuration

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

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

  sudo zypper al python312-pip

• 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 python312-pip — vulnerability — patch and remediation guide: 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-leap-15-6 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Primary reference: SUSE advisory SUSE-CU-2023:4334-1 (see also SUSE bugzilla). Manual pages useful on openSUSE Leap 15.6:

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/python312-pip/ for components implicated in python312-pip — vulnerability — patch and remediation guide.

View all openSUSE Leap 15.6 tutorials on the Tutorials Hub →