# 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


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 17 May 2023
- **Updated:** 22 Jan 2025
- **Also known as:** GHSA-6rhm-fw89-rh2q

## What is CVE-2023-2319?

CVE-2023-2319 is a critical vulnerability in pcs, published on 17 May 2023. 

### Official description

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 include the fix for the Webpack issue CVE-2023-28154 (for PCS package), which was previously addressed in Red Hat Enterprise Linux 9.1 via erratum RHSA-2023:1591. The CVE-2023-2319 was assigned to that Red Hat specific security regression in Red Hat Enterprise Linux 9.2.

## Which versions are affected by CVE-2023-2319?

It affects 3 products.


Products: Clusterlabs Pcs, Redhat Enterprise Linux High Availability, Redhat Enterprise Linux High Availability Eus.

## How do I fix CVE-2023-2319?

Upgrade to a fixed version.

## Is CVE-2023-2319 being exploited?

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

## Other vulnerabilities in pcs

- [CVE-2022-1049](https://insights.sbomify.com/CVE-2022-1049/): Auth bypass in clusterlabs/pcs (high 8.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-2023-2319 and fix it if it is affected.

What it is: CVE-2023-2319 is a critical vulnerability in pcs, published on 17 May 2023. 
Exploitation: There is no known exploitation of CVE-2023-2319 in the wild and no public exploit code.

Affected product: pcs. 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-2023-2319/ (Markdown: https://insights.sbomify.com/CVE-2023-2319/index.md)
```

## Sources

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

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