# ALBA-2021:0550: pcp bug fix and enhancement update

> Bug fixes for Performance Co-Pilot address service startup failures and duplicate metric logging issues.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 16 Feb 2021

## What is ALBA-2021:0550?

ALBA-2021:0550 is a vulnerability in pcp, published on 16 Feb 2021. 

### Official description

Performance Co-Pilot (PCP) is a suite of tools, services, and libraries for
acquisition, archiving, and analysis of system-level performance
measurements. Its light-weight distributed architecture makes it
particularly well-suited to centralized analysis of complex systems.

Bug Fix(es) and Enhancement(s):

* NetworkManager.service can not be started with  probability after reboot
(BZ#1916385)

* pmlogger: some metrics get logged twice (BZ#1917775)

## Which versions are affected by ALBA-2021:0550?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pcp` | AlmaLinux:8 | All versions | 5.1.1-4.el8_3 |
| `pcp-conf` | AlmaLinux:8 | All versions | 5.1.1-4.el8_3 |
| `pcp-libs` | AlmaLinux:8 | All versions | 5.1.1-4.el8_3 |
| `pcp-manager` | AlmaLinux:8 | All versions | 5.1.1-4.el8_3 |
| `pcp-selinux` | AlmaLinux:8 | All versions | 5.1.1-4.el8_3 |

## How do I fix ALBA-2021:0550?

Apply the vendor's patch.

## Is ALBA-2021:0550 being exploited?

There is no known exploitation of ALBA-2021:0550 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for ALBA-2021:0550 and fix it if it is affected.

What it is: ALBA-2021:0550 is a vulnerability in pcp, published on 16 Feb 2021. 
Exploitation: There is no known exploitation of ALBA-2021:0550 in the wild and no public exploit code.

Affected product: pcp. 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/ALBA-2021-0550/ (Markdown: https://insights.sbomify.com/ALBA-2021-0550/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/ALBA-2021:0550

---
From sbomify Insights: https://insights.sbomify.com/ALBA-2021-0550/
Summaries are generated and may contain mistakes; the official description above is the record.