SUSE-SU-2025:1193-1 Security update for apparmor
Not scored
Published
Check this codebase for SUSE-SU-2025:1193-1 and fix it if it is affected.
What it is: SUSE-SU-2025:1193-1 is a vulnerability in apparmor, published on 10 Apr 2025.
Exploitation: There is no known exploitation of SUSE-SU-2025:1193-1 in the wild and no public exploit code.
Affected product: apparmor. 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-2025-1193-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2025-1193-1/index.md)
AppArmor policy update allows Dovecot authentication to execute from /sbin, correcting a path restriction that could hinder legitimate authentication processes.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- Available
What is SUSE-SU-2025:1193-1?
SUSE-SU-2025:1193-1 is a vulnerability in apparmor, published on 10 Apr 2025.
Official description
This update for apparmor fixes the following issue:
- Allow dovecot-auth to execute unix check password from /sbin, not only from /usr/bin (bsc#1234452).
Which versions are affected by SUSE-SU-2025:1193-1?
Linux distribution packages (16)
apparmor SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 3.0.4-150400.5.12.2 |
libapparmor SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 3.0.4-150400.5.12.2 |
apparmor SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 3.0.4-150400.5.12.2 |
libapparmor SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 3.0.4-150400.5.12.2 |
apparmor SUSE:Linux Enterprise Micro 5.3 | All versions | 3.0.4-150400.5.12.2 |
libapparmor SUSE:Linux Enterprise Micro 5.3 | All versions | 3.0.4-150400.5.12.2 |
apparmor SUSE:Linux Enterprise Micro 5.4 | All versions | 3.0.4-150400.5.12.2 |
libapparmor SUSE:Linux Enterprise Micro 5.4 | All versions | 3.0.4-150400.5.12.2 |
apparmor SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 3.0.4-150400.5.12.2 |
libapparmor SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 3.0.4-150400.5.12.2 |
apparmor SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 3.0.4-150400.5.12.2 |
libapparmor SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 3.0.4-150400.5.12.2 |
apparmor SUSE:Manager Proxy 4.3 | All versions | 3.0.4-150400.5.12.2 |
libapparmor SUSE:Manager Proxy 4.3 | All versions | 3.0.4-150400.5.12.2 |
apparmor SUSE:Manager Server 4.3 | All versions | 3.0.4-150400.5.12.2 |
libapparmor SUSE:Manager Server 4.3 | All versions | 3.0.4-150400.5.12.2 |
How do I fix SUSE-SU-2025:1193-1?
Apply the vendor's patch.
Is SUSE-SU-2025:1193-1 being exploited?
There is no known exploitation of SUSE-SU-2025:1193-1 in the wild and no public exploit code.