google / google/csp-evaluator

Frame Ancestors are allowed to have non-leading wildcards

Open
#58 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
404
Forks
59
PR merge metrics
No merged PRs in 30d

Description

As described on MDN (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors#sources), any wildcards used in a source for the frame-ancestors directive must be leading. However, CSP Evaluator does not flag when a non-leading wildcard is used, and instead says it is all good:
![image](https://user-images.githubusercontent.com/58530748/236894618-8568f566-55d0-4fa1-8797-ce0649edb809.png)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.