commit 1b315615e7dc61dbf845bd663560fc8d5a18fa09
Author: Jay Faulkner <email address hidden>
Date: Thu Aug 10 11:28:32 2023 -0700
Only allow safe context fields in notifications
Publishing a fully hydrated context object in a notification would give
someone with access to that notification the ability to impersonate the
original actor through inclusion of sensitive fields.
Now, instead, we pare down the context object to the bare minimum before
passing it for serialization in notification workflows.
Reviewed: https:/ /review. opendev. org/c/openstack /oslo.messaging /+/891096 /opendev. org/openstack/ oslo.messaging/ commit/ 1b315615e7dc61d bf845bd663560fc 8d5a18fa09
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 1b315615e7dc61d bf845bd663560fc 8d5a18fa09
Author: Jay Faulkner <email address hidden>
Date: Thu Aug 10 11:28:32 2023 -0700
Only allow safe context fields in notifications
Publishing a fully hydrated context object in a notification would give
someone with access to that notification the ability to impersonate the
original actor through inclusion of sensitive fields.
Now, instead, we pare down the context object to the bare minimum before
passing it for serialization in notification workflows.
Related-bug: 2030976 1c1ff32f511ca23 502317d0f00
Change-Id: Ic94323658c89df