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

[Backport 2.1] Use a forced CSP-compliant interpreter with Vega visualizations #2372

Merged
merged 1 commit into from
Sep 16, 2022

Conversation

opensearch-trigger-bot[bot]
Copy link
Contributor

Backport bebbcca from #2352

* Pass `options` to `vega.parse` to enable inclusion of parsed ASTs
* Introduce the forced CSP-compliant interpreter that prevents evaluation of unsafe methods
* Modified the consumed `leaflet-vega` package to one that honors `options`

Signed-off-by: Miki <miki@amazon.com>

Signed-off-by: Miki <miki@amazon.com>
(cherry picked from commit bebbcca)
@opensearch-trigger-bot opensearch-trigger-bot bot requested a review from a team as a code owner September 15, 2022 18:42
Copy link
Member

@joshuarrrr joshuarrrr left a comment

Choose a reason for hiding this comment

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

Just a note - I think this is worth merging despite the fact that it may be a "breaking" change for some user that relied on the insecure behavior.

@joshuarrrr joshuarrrr merged commit 84b2b7a into 2.1 Sep 16, 2022
@joshuarrrr joshuarrrr deleted the backport/backport-2352-to-2.1 branch September 16, 2022 00:40
@ashwin-pc
Copy link
Member

@joshuarrrr I dont think that can be considered breaking change since relying on insecure behaviour is a security risk that we should not support and that the user should probably figure out a way to get out of

@joshuarrrr
Copy link
Member

Yeah, that's exactly what I meant, just wanted to point out that it has the potential to break some user workflows, and force them to adapt. But absolutely worth doing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants