dbcve.org
Enterprise Linux High AvailabilityOperating system · Redhat

CVE-2023-2319

CRITICAL · 9.8 CVSS v3.1 Published 2023-05-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Red Hat-specific security regression in RHEL 9.2. The PCS package update (RHBA-2023:2151) failed to include the previously available fix for CVE-2023-28154 (a Webpack vulnerability), creating a regression where the critical vulnerability reintroduced itself in the 9.2 release despite having been fixed in RHEL 9.1 via RHSA-2023:1591.

MitigationApply the corrected PCS package update for RHEL 9.2 that includes the fix for CVE-2023-28154. Organizations should ensure they are on the latest errata that properly include the Webpack vulnerability fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise Linux High AvailabilityOperating system
Affected:= 9.0
Enterprise Linux High Availability EusOperating system
Affected:= 9.2
PcsApplication
Affected:= 0.11.4-6.el9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify PCS package is installed
    Run: rpm -qa | grep -i pcs
    Affected if The pcs package is not installed, then this CVE does not apply. If installed, continue to next step.
  2. Check installed PCS version
    Run: rpm -q --queryformat '%{VERSION}-%{RELEASE}' pcs
    Affected if Version matches 0.11.4-6.el9 or falls within the affected RHEL 9.0/9.2 High Availability ranges, indicating the regression is present.
  3. Confirm Webpack vulnerability status
    Run: rpm -q --changelog pcs | grep -i 'CVE-2023-28154\|webpack'
    Affected if No output returned means the CVE-2023-28154 fix is NOT present (the regression applies). If the changelog shows the fix for CVE-2023-28154, the system is protected.
  4. Alternative: Check for vulnerable Webpack files
    Locate webpack JavaScript files under /usr/lib/pcs/drf/ or /usr/share/pcs/drf/ and check their content for known vulnerable patterns (的具体内容需参照CVE-2023-28154)
    Affected if Vulnerable webpack files exist without the security fix applied.

If PCS version 0.11.4-6.el9 is installed on RHEL 9.2 and the changelog does not show CVE-2023-28154 as fixed, the system is affected by this regression.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the corrected PCS package update for RHEL 9.2 that includes the fix for CVE-2023-28154. Organizations should ensure they are on the latest errata that properly include the Webpack vulnerability fix.

Recommended fix Moderate confidence

Latest available PCS package via Red Hat update channels (later than 0.11.4-6.el9, incorporating the CVE-2023-28154 fix)

  1. Run 'dnf check-update' or 'yum update' to check for available PCS updates
  2. Update the PCS package using 'sudo dnf update pcs' or 'sudo yum update pcs'
  3. After updating, verify the new version with 'rpm -q pcs' to confirm the fix is applied
  4. Restart any PCS services if necessary to load the updated package
Caveat Standard package update - minimal risk; as a security fix, should not introduce functional changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Linux High Availability Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2319 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-2319 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data