GHSA-hgv4-xx36-g3vf: 
Python vulnerability analysis and mitigation

Impact

run_secure_consortium_round and run_god_consortium_round ran n-of-m MPA authorization only after the survivor set was anchored, recovery shares were revealed and the aggregate was computed. An unauthorized round therefore still produced the aggregate in the coordinator process, and a round rejected by the robustness gate returned its aggregate to the caller without authorization having run. The governed v1 round (run_consortium_round, used by pai consortium-round) was not affected.

Patches

Fixed in 0.32.1: both rounds authorize on the worst-case epsilon first (the GOD round over every submitting party), so an unauthorized round anchors, deals and aggregates nothing.

Workarounds

Call authorize_request for the round's worst-case DP result before invoking either round function.