acacode / acacode/swagger-typescript-api

Cannot apply `require-trusted-types-for 'script'` Content-Security-Policy

Aberta
#985 0 comentários 0 reações 0 responsáveis Ver no GitHub
enhancement
Linguagem predominante
TypeScript
Estrelas
4.1k
Forks
436
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

Our SOC-2 auditor identified a vulnerability risk with our content security policy because we didn't have explicit list of `trusted-types` in our application's Content-Security-Policy. In theory, if a 0-day exploit was found, someone could inject malicious javascript into the page and the Content-Security-Policy would block ordinary users from seeing it unless they manually edited the local response headers. The CSP acts as a last line of defense against XSS.

The usual fix is to add `require-trusted-types-for 'script'` to our CSP, find which elements it is blocking and whitelist them. However, this does not work on the docs page because the elements rendered by the Swagger Docs do not have a `trustedType` associated with them to whitelist.

We do not have a lot of frontend resources available at the moment, so wrapping everything in the frontend code in our own trusted types would be a heavy lift as a workaround. What I would like is for the swagger components to have their own trustedType(s) that I can whitelist on the `trusted-types` section of the CSP so the docs page will actually render instead of looking like this:

![Screenshot 2024-11-18 at 1 03 49 PM](https://github.com/user-attachments/assets/9246fe80-cc07-4445-982d-d693a287e34c)

Guia de contribuição

Nenhum guia de contribuição indexado para este repositório

Avaliação

Esta issue ainda não foi avaliada.

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.