Ceph StorageApplication · Redhat
CVE-2019-19337
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 Red Hat Ceph Storage version 3 in the way the Ceph RADOS Gateway daemon handles S3 requests. An authenticated attacker can abuse this flaw by causing a remote denial of service by sending a specially crafted HTTP Content-Length header to the Ceph RADOS Gateway server.
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 denial of service vulnerability exists in Red Hat Ceph Storage 3's RADOS Gateway (RGW) daemon. The flaw is in how the RGW handles S3 requests, specifically when processing a specially crafted HTTP Content-Length header. An authenticated attacker can send this malicious request to cause the RGW to crash or become unresponsive.
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
= 3.3CVSS 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.
-
Identify installed Ceph Storage versionRun 'ceph --version' or check the RPM package version with 'rpm -q ceph-common' or 'rpm -q ceph-ansible' to determine the exact version of Ceph Storage deployedAffected if The version is Red Hat Ceph Storage 3.3 (or any 3.x version that has not received the security update)
-
Verify RGW daemon is activeCheck if the RADOS Gateway service is running with 'systemctl status ceph-radosgw@*' or 'ceph -s' to confirm the RGW daemon is deployed and activeAffected if RGW is running and exposed as part of the Ceph Storage deployment
-
Confirm RGW is reachable over networkCheck RGW configuration files in /etc/ceph/ and look for 'rgw_frontends' settings, or use 'ceph config get mon rgw_enable_ops_log' to verify RGW is configured to accept HTTP connectionsAffected if RGW is bound to a network interface and accepting S3 API connections (typically on ports 80/443 or 7480)
-
Review authentication configurationExamine RGW user database or integration with LDAP/Active Directory by checking /etc/ceph/rgw*.keyring or RGW configuration for 'rgw_s3_auth_use_ldap' and similar settingsAffected if External authentication is enabled allowing authenticated S3 users to send requests
-
Check for crash or unavailability eventsReview Ceph logs in /var/log/ceph/ceph-rgw*.log and system logs for recent RGW crashes, timeouts, or restart events, especially around the time of suspicious requestsAffected if RGW has recently crashed, restarted unexpectedly, or become unresponsive without clear cause
A system is affected if it runs Red Hat Ceph Storage 3.3 with the RGW daemon active and reachable, where an authenticated attacker could send a crafted Content-Length header to cause denial of service.
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 dataApply the Red Hat security update for CVE-2019-19337 to Red Hat Ceph Storage 3. If patching is not immediately possible, consider restricting RGW access to trusted users and implementing rate limiting as a temporary workaround.
Fix this in Ceph Storage
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19337 — 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-2019-19337 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