Openshift Container StorageApplication · Redhat
CVE-2020-1700
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 · uneditedA flaw was found in the way the Ceph RGW Beast front-end handles unexpected disconnects. An authenticated attacker can abuse this flaw by making multiple disconnect attempts resulting in a permanent leak of a socket connection by radosgw. This flaw could lead to a denial of service condition by pile up of CLOSE_WAIT sockets, eventually leading to the exhaustion of available resources, preventing legitimate users from connecting to the system.
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 · high confidenceA socket handling flaw in the Ceph RGW Beast front-end causes permanent leaks of socket connections when unexpected disconnects occur. An authenticated attacker can trigger this by making multiple disconnect attempts, accumulating CLOSE_WAIT sockets until system resources are exhausted, resulting in denial of service.
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
Openshift Container StorageApplication
= 4.2
Ubuntu LinuxOperating system
= 18.04= 19.10all versions= 15.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Ceph RGW is deployedCheck for running radosgw processes or query the Ceph cluster for RGW instances: `ceph orch ps | grep rgw` or `ps aux | grep radosgw`Affected if No RGW deployed means not affected by this specific RGW vulnerability
-
Confirm Beast front-end is enabledExamine RGW configuration for the 'beast' front-end setting in ceph.conf or the running container/daemon configuration. Look for `rgw_frontends = beast` or similar beast-related frontend configuration.Affected if The vulnerability only affects the Beast front-end; other front-ends (civetweb) are not vulnerable to this specific flaw
-
Check for CLOSE_WAIT socket accumulationRun `netstat -an | grep CLOSE_WAIT | grep <rgw_port>` or `ss -tan state close-wait | grep <rgw_port>` repeatedly over time to observe if the count grows persistently without drainingAffected if Sustained growth of CLOSE_WAIT sockets associated with RGW ports indicates active exploitation or vulnerability presence
-
Determine installed Ceph versionQuery the Ceph version with `ceph --version` or `ceph version` command, or check the package version installed on the RGW hostAffected if All versions of Ceph are listed as affected; any RGW deployment with Beast front-end on any version is potentially vulnerable
If Ceph RGW is running with the Beast front-end enabled and CLOSE_WAIT sockets are accumulating on RGW ports, the environment is affected by this socket leak vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of Ceph that addresses the socket leak in the RGW Beast front-end connection handling, as this is a code-level bug requiring a software update.
Fix this in Openshift Container Storage
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1700 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-1700 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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