Bug 1644461 (CVE-2018-16846) - CVE-2018-16846 ceph: ListBucket max-keys has no defined limit in the RGW codebase
Summary: CVE-2018-16846 ceph: ListBucket max-keys has no defined limit in the RGW code...
Status: NEW
Alias: CVE-2018-16846
Product: Security Response
Classification: Other
Component: vulnerability   
(Show other bugs)
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=moderate,public=20190107,repor...
Keywords: Security
Depends On: 1645052 1645053 1665973
Blocks: 1644462
TreeView+ depends on / blocked
 
Reported: 2018-10-30 21:35 UTC by Pedro Sampaio
Modified: 2019-03-05 04:11 UTC (History)
22 users (show)

Fixed In Version: ceph 13.2.4
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the way the ListBucket function max-keys has no defined limit in the RGW codebase. An authenticated ceph RGW user can cause a denial of service attack against OMAPs holding bucked indices.
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Ceph Project Bug Tracker 35994 None None None 2018-11-27 19:17 UTC

Description Pedro Sampaio 2018-10-30 21:35:30 UTC
RGW S3 listing operations provided a way for authenticated users to cause a denial of service against OMAPs holding bucket indices.

References:

http://tracker.ceph.com/issues/35994

Comment 3 Siddharth Sharma 2019-01-14 15:18:41 UTC
External References:

https://ceph.com/releases/13-2-4-mimic-released/

Comment 4 Siddharth Sharma 2019-01-14 15:26:45 UTC
Created ceph tracking bugs for this issue:

Affects: fedora-all [bug 1665973]

Comment 5 Siddharth Sharma 2019-01-15 03:49:08 UTC
upstream fix

https://github.com/ceph/ceph/commit/ab29bed2fc9f961fe895de1086a8208e21ddaddc


Note You need to log in before you can comment on or make changes to this bug.