dbcve.org
Ceph StorageApplication · Redhat

CVE-2023-0056

MEDIUM · 6.5 CVSS v3.1 Published 2023-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
An uncontrolled resource consumption vulnerability was discovered in HAProxy which could crash the service. This issue could allow an authenticated remote attacker to run a specially crafted malicious server in an OpenShift cluster. The biggest impact is to availability.

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

An uncontrolled resource consumption vulnerability in HAProxy allows an authenticated remote attacker to deploy a specially crafted malicious server in an OpenShift cluster, causing HAProxy to crash due to resource exhaustion. The vulnerability requires authentication, which somewhat limits the attack surface, but once exploited it results in complete service unavailability.

MitigationApply proper HAProxy resource limits, connection timeouts, and backend server constraints in the OpenShift environment. Update HAProxy to the latest version if a patch is available, and implement rate limiting and max connections controls for backend servers.

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
Ceph StorageApplication
Affected:= 5.0
Software CollectionsApplication
Affected:all versions
Openshift Container PlatformApplication
Affected:= 4.12= 4.10= 4.11
Openshift Container Platform For Ibm LinuxoneApplication
Affected:= 4.12= 4.10= 4.11
Openshift Container Platform For PowerApplication
Affected:= 4.12= 4.10= 4.11
Openshift Container Platform Ibm Z SystemsApplication
Affected:= 4.12= 4.10= 4.11
FedoraOperating system
Affected:= 36= 37
HaproxyWeb server / proxy
Affected:all versions

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify HAProxy version
    Run 'haproxy -v' or check the installed package version (e.g., rpm -q haproxy, dpkg -l haproxy)
    Affected if The installed version matches any of the affected products (all versions of HAProxy are affected per the CVE data)
  2. Confirm OpenShift environment
    Check if HAProxy is running within an OpenShift cluster (oc cluster-info, oc get nodes, or check for openshift-specific namespaces/pods)
    Affected if HAProxy is deployed in Red Hat OpenShift Container Platform versions 4.10, 4.11, or 4.12, or any OpenShift variant for IBM LinuxONE, Power, or Z Systems at those versions
  3. Verify authentication exposure
    Determine if HAProxy management or backend server configuration is accessible to authenticated users (check OpenShift RBAC policies, router configurations, or whether users can modify backend server definitions)
    Affected if Authenticated users can deploy or modify backend server configurations in the HAProxy setup
  4. Inspect resource limit configurations
    Review HAProxy configuration files for backend server constraints, connection timeouts, and max connections settings (typically in /etc/haproxy/haproxy.cfg or OpenShift router config)
    Affected if No resource limits, connection timeouts, or backend server constraints are configured, allowing uncontrolled resource consumption by a malicious server

You are affected if HAProxy is running in an OpenShift environment (versions 4.10-4.12) or as part of the listed Red Hat products, and authenticated users can deploy backend servers without proper resource limits configured.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply proper HAProxy resource limits, connection timeouts, and backend server constraints in the OpenShift environment. Update HAProxy to the latest version if a patch is available, and implement rate limiting and max connections controls for backend servers.

Fix this in Ceph Storage Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0056 — 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-0056 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