:warning: Security Advisory- Re: PDP secret manage...
# announcements
o
⚠️ Security Advisory- Re: PDP secret managements ⚠️ TL;DR: Some configurations of PDP could have led to some OPAL-client routes being unauthenticated. The issue has been resolved going forward by a remote configuration push by our sec team. Action required: Restart your PDPs if they’re older than 0.5.6-rc.1 (to apply new configuration) Additional recommendations: • Upgrading to the latest version of the PDP • Always make sure your PDPs are not open to the internet (this remains the best practice regardless) • If your PDPs were exposed directly to the internet - we recommend rotating the keys for their associated environments/projects and redeploying them with the new key Details: Recent findings have shown that in some configurations of the PDP / matching Permit environments public keys haven’t been passed to the OPAL-client inside the PDP leading to routes within the OPAL-client being unauthenticated. The team has responded to investigate this issue quickly and has been able to address this issue for all customers remotely via a configuration push (which only requires a con. In addition we’ve released a new version of the PDP that includes a default public-key as an extra precaution. We recommend customers upgrade their PDPs to this latest version, and rotate their environment keys (this can be done via the Projects screen / via the API) You’re welcome to follow up on this thread or in a DM (@Asaf Cohen) with further questions. We are also available to you via Zoom here , and via email at help@permit.io Thanks to @Tyler Queen for reporting this issue (we got some swag coming your way) Slack Conversation