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

Missing security related headers for static resources serving from the Presto UI #24271

Open
yhwang opened this issue Dec 17, 2024 · 1 comment · May be fixed by #24272
Open

Missing security related headers for static resources serving from the Presto UI #24271

yhwang opened this issue Dec 17, 2024 · 1 comment · May be fixed by #24272
Assignees
Labels

Comments

@yhwang
Copy link
Member

yhwang commented Dec 17, 2024

Missing the following security-related headers:

  • Content-Security-Policy
    Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate
    certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks.
    These attacks are used for everything from data theft to site defacement or distribution of
    malware. CSP provides a set of standard HTTP headers that allow website owners to
    declare approved sources of content that browsers should be allowed to load on that page
    — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable
    objects such as Java applets, ActiveX, audio and video files.
  • X-Content-Type-Options
    The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows
    older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response
    body, potentially causing the response body to be interpreted and displayed as a content
    type other than the declared content type. Current (early 2014) and legacy versions of
    Firefox will use the declared content type (if one is set), rather than performing MIME-
    sniffing.

Your Environment

  • Presto version used: 0.291

Expected Behavior

For those static resources, they should contain Content-Security-Policy and X-Content-Type-Options headers in the response

Current Behavior

None of the headers exist in the responses of the static resources

Possible Solution

Add these two headers for the static resources.

@yhwang yhwang added the bug label Dec 17, 2024
@yhwang yhwang self-assigned this Dec 17, 2024
@github-project-automation github-project-automation bot moved this to 🆕 Unprioritized in Bugs and support requests Dec 17, 2024
@yhwang yhwang linked a pull request Dec 17, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🆕 Unprioritized
Development

Successfully merging a pull request may close this issue.

1 participant