# CVE-2022-1049: Auth bypass in clusterlabs/pcs

> The pcs daemon allows login for expired accounts or passwords via PAM, bypassing access restrictions for unprivileged users.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** ALSA-2022:7447, ALSA-2022:7935, DEBIAN-CVE-2022-1049, DLA-3108-1, GHSA-hhh9-rwf2-2pp5, OESA-2022-1886, RHSA-2022:7447, RHSA-2022:7935, RLSA-2022:7447, RLSA-2022:7935, UBUNTU-CVE-2022-1049

## What is CVE-2022-1049?

CVE-2022-1049 is a high-severity authentication bypass vulnerability in Debian Debian Linux, published on 25 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the Pacemaker configuration tool (pcs). The pcs daemon was allowing expired accounts, and accounts with expired passwords to login when using PAM authentication. Therefore, unprivileged expired accounts that have been denied access could still login.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-1049?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pcs` | AlmaLinux:8 | All versions | 0.10.14-5.el8.alma |
| `pcs-snmp` | AlmaLinux:8 | All versions | 0.10.14-5.el8.alma |
| `pcs` | AlmaLinux:9 | All versions | 0.11.3-4.el9 |
| `pcs-snmp` | AlmaLinux:9 | All versions | 0.11.3-4.el9 |
| `pcs` | Red Hat:enterprise_linux:8::highavailability | All versions | 0:0.10.14-5.el8 |
| `pcs-snmp` | Red Hat:enterprise_linux:8::highavailability | All versions | 0:0.10.14-5.el8 |
| `pcs` | Red Hat:enterprise_linux:8::resilientstorage | All versions | 0:0.10.14-5.el8 |
| `pcs-snmp` | Red Hat:enterprise_linux:8::resilientstorage | All versions | 0:0.10.14-5.el8 |
| `pcs` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:0.11.3-4.el9 |
| `pcs-snmp` | Red Hat:enterprise_linux:9::highavailability | All versions | 0:0.11.3-4.el9 |
| `pcs` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:0.11.3-4.el9 |
| `pcs-snmp` | Red Hat:enterprise_linux:9::resilientstorage | All versions | 0:0.11.3-4.el9 |
| `pcs` | Rocky Linux:8 | All versions | 0:0.10.14-5.el8 |
| `pcs` | Rocky Linux:9 | All versions | 0:0.11.3-4.el9_1.1 |

Products: Clusterlabs Pcs, Debian Debian Linux.

## How do I fix CVE-2022-1049?

Apply the vendor's patch.

## Is CVE-2022-1049 being exploited?

There is no known exploitation of CVE-2022-1049 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2023-2319](https://insights.sbomify.com/CVE-2023-2319/): It was discovered that an update for PCS package in RHBA-2023:2151 erratum released as part of Red Hat Enterprise Linux 9.2 failed to includ (critical 9.8)
- [CVE-2016-0720](https://insights.sbomify.com/CVE-2016-0720/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-0721](https://insights.sbomify.com/CVE-2016-0721/): Other in n/a (high 8.1)
- [CVE-2022-2735](https://insights.sbomify.com/CVE-2022-2735/): Privilege escalation in ClusterLabs/pcs (high 7.8)
- [CVE-2017-2661](https://insights.sbomify.com/CVE-2017-2661/): Cross-site scripting in pcs (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1049 and fix it if it is affected.

What it is: CVE-2022-1049 is a high-severity authentication bypass vulnerability in Debian Debian Linux, published on 25 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1049 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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/CVE-2022-1049/ (Markdown: https://insights.sbomify.com/CVE-2022-1049/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1049
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1049
- OSV: https://osv.dev/vulnerability/CVE-2022-1049

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