# SUSE-SU-2020:1857-1: Security update for permissions

> An attacker could exploit conflicting permission entries to bypass security controls in the Performance Co-Pilot (PCP) package on SUSE Linux.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jul 2020

## What is SUSE-SU-2020:1857-1?

SUSE-SU-2020:1857-1 is a vulnerability in permissions, published on 6 Jul 2020. 

### Official description

This update for permissions fixes the following issues:

- Removed conflicting entries which might expose pcp to security issues (bsc#1171883)

## Which versions are affected by SUSE-SU-2020:1857-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `permissions` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 20170707-3.24.1 |
| `permissions` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 20170707-3.24.1 |

## How do I fix SUSE-SU-2020:1857-1?

Apply the vendor's patch.

## Is SUSE-SU-2020:1857-1 being exploited?

There is no known exploitation of SUSE-SU-2020:1857-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2020:1857-1 and fix it if it is affected.

What it is: SUSE-SU-2020:1857-1 is a vulnerability in permissions, published on 6 Jul 2020. 
Exploitation: There is no known exploitation of SUSE-SU-2020:1857-1 in the wild and no public exploit code.

Affected product: permissions. 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-2020-1857-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2020-1857-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2020:1857-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2020-1857-1/
Summaries are generated and may contain mistakes; the official description above is the record.