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 of [Security] Fix XSS Vulnerability where content-type header wasn't explicitly set into release/1.19.x #21709

Conversation

hc-github-team-consul-core
Copy link
Collaborator

Backport

This PR is auto-generated from #21704 to be assessed for backporting due to the inclusion of the label backport/1.19.

The below text is copied from the body of the original PR.


Description

Added middleware to ensure that content-type header is always set to mitigate XSS vulnerability.

Testing & Reproduction steps

  • Updated unit tests to add additional checks for content-type header
  • Vercel should deploy UI with no errors

Links

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

Overview of commits

@hc-github-team-consul-core hc-github-team-consul-core force-pushed the backport/SECVULN-8619-TOB-CONSUL24-3-Reflected-XSS-in-peering-endpoints-that-return-an-error/wholly-mint-jennet branch from 626d739 to 9874595 Compare September 11, 2024 19:24
Copy link
Collaborator

Choose a reason for hiding this comment

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

Auto approved Consul Bot automated PR

@dduzgun-security dduzgun-security merged commit 18354fc into release/1.19.x Sep 13, 2024
104 checks passed
@dduzgun-security dduzgun-security deleted the backport/SECVULN-8619-TOB-CONSUL24-3-Reflected-XSS-in-peering-endpoints-that-return-an-error/wholly-mint-jennet branch September 13, 2024 15:22
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.

4 participants