Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc/releases/mimic: v13.2.4 #25793

Merged
merged 6 commits into from Jan 4, 2019
Merged

doc/releases/mimic: v13.2.4 #25793

merged 6 commits into from Jan 4, 2019

Conversation

liewegas
Copy link
Member

@liewegas liewegas commented Jan 4, 2019

Signed-off-by: Sage Weil sage@redhat.com


CVE-2018-14662
CVE-2018-16846

jecluis and others added 3 commits October 17, 2018 14:42
Henceforth, we'll require explicit `allow` caps for commands, or for the
config-key service. Blanket caps are no longer allowed for the
config-key service, except for 'allow *'.

Signed-off-by: Joao Eduardo Luis <joao@suse.de>
RGW S3 listing operations provided a way for authenticated users to
cause a denial of service against OMAPs holding bucket indices.

Bound the min & max values that a user could pass into the max-X
parameters, to keep the system safe. The default of 1000 is chosen to
match AWS S3 behavior.

Affected operations:
- ListBucket, via max-keys
- ListBucketVersions, via max-keys
- ListBucketMultiPartUploads, via max-uploads
- ListMultipartUploadParts, via max-parts

The Swift bucket listing codepath already enforced a limit, so is
unaffected by this issue.

Prior to this commit, the effective limit is the lower of
osd_max_omap_entries_per_request or osd_max_omap_bytes_per_request.

Backport: luminous, mimic
Fixes: http://tracker.ceph.com/issues/35994
Signed-off-by: Robin H. Johnson <rjohnson@digitalocean.com>
The patch to enforce bounds on max-keys/max-uploads/max-parts had a few
issues that would prevent us from compiling it. Instead of changing the
code provided by the submitter, we're addressing them in a separate
commit to maintain the DCO.

Signed-off-by: Joao Eduardo Luis <joao@suse.de>
Copy link

@djgalloway djgalloway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/inadvertantly/inadvertently

Signed-off-by: Sage Weil <sage@redhat.com>
Copy link
Member

@gregsfortytwo gregsfortytwo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not real familiar with the tests, but looks fine!

Reviewed-by: Greg Farnum gfarnum@redhat.com

@liewegas liewegas merged commit e069c30 into ceph:master Jan 4, 2019
liewegas added a commit that referenced this pull request Jan 4, 2019
* refs/pull/25793/head:
	Merge remote-tracking branch 'private/wip-mon-kv-fix' into wip-mimic-4
	Merge remote-tracking branch 'private/wip-rgw-max-keys' into wip-mimic-4
	doc/releases/mimic: v13.2.4
	rgw: fix issues with 'enforce bounds' patch
	rgw: enforce bounds on max-keys/max-uploads/max-parts
	mon/config-key: limit caps allowed to access the store

Reviewed-by: Gregory Farnum <gfarnum@redhat.com>
Reviewed-by: David Galloway <dgallowa@redhat.com>
Reviewed-by: Greg Farnum <gfarnum@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants