SUSE-SU-2022:4278-1 Security update for supportutils
Not scored
Published
Check this codebase for SUSE-SU-2022:4278-1 and fix it if it is affected.
What it is: SUSE-SU-2022:4278-1 is a vulnerability in supportutils, published on 29 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2022:4278-1 in the wild and no public exploit code.
Affected product: supportutils. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/SUSE-SU-2022-4278-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2022-4278-1/index.md)
An attacker with local access can read sensitive passwords from supportutils log files due to improper data sanitization.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is SUSE-SU-2022:4278-1?
SUSE-SU-2022:4278-1 is a vulnerability in supportutils, published on 29 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
This update for supportutils fixes the following issues:
Security issues fixed:
- Passwords correctly removed from email.txt, updates.txt and fs-iscsi.txt (bsc#1203818)
Bug fixes:
- Added lifecycle information
- Fixed KVM virtualization detection on bare metal (bsc#1184689)
- Added logging using journalctl (bsc#1200330)
- Get current sar data before collecting files (bsc#1192648)
- Collects everything in /etc/multipath/ (bsc#1192252)
- Collects power management information in hardware.txt (bsc#1197428)
- Checks for suseconnect-ng or SUSEConnect packages (bsc#1202337)
- Fixed conf_files and conf_text_files so y2log is gathered (bsc#1202269)
- Update to nvme_info and block_info (bsc#1202417)
- Added includedir directories from /etc/sudoers (bsc#1188086)
Which versions are affected by SUSE-SU-2022:4278-1?
Linux distribution packages (9)
supportutils SUSE:Linux Enterprise Micro 5.1 | All versions | 3.1.21-150300.7.35.15.1 |
supportutils SUSE:Linux Enterprise Micro 5.2 | All versions | 3.1.21-150300.7.35.15.1 |
supportutils SUSE:Linux Enterprise Micro 5.3 | All versions | 3.1.21-150300.7.35.15.1 |
supportutils SUSE:Linux Enterprise Module for Basesystem 15 SP3 | All versions | 3.1.21-150300.7.35.15.1 |
supportutils SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 3.1.21-150300.7.35.15.1 |
supportutils openSUSE:Leap 15.3 | All versions | 3.1.21-150300.7.35.15.1 |
supportutils openSUSE:Leap 15.4 | All versions | 3.1.21-150300.7.35.15.1 |
supportutils openSUSE:Leap Micro 5.2 | All versions | 3.1.21-150300.7.35.15.1 |
supportutils openSUSE:Leap Micro 5.3 | All versions | 3.1.21-150300.7.35.15.1 |
How do I fix SUSE-SU-2022:4278-1?
Apply the vendor's patch.
Is SUSE-SU-2022:4278-1 being exploited?
There is no known exploitation of SUSE-SU-2022:4278-1 in the wild and no public exploit code.