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

XSS vulnerability in the All Variables tab #3919

Closed
michaelnoonan opened this issue Nov 14, 2017 · 3 comments
Closed

XSS vulnerability in the All Variables tab #3919

michaelnoonan opened this issue Nov 14, 2017 · 3 comments
Assignees
Labels
kind/bug This issue represents a verified problem we are committed to solving priority (obsolete) This issue has been recognised as a priority and should be addressed as soon as possible
Milestone

Comments

@michaelnoonan
Copy link
Contributor

michaelnoonan commented Nov 14, 2017

See https://github.com/OctopusDeploy/OctopusDeploy/issues/1101

CVE-2017-16810

source: https://secure.helpscout.net/conversation/367176482

Steps to recreate:

  1. Create a new variable set

  2. Put your XSS payload in the name of the variable set, for example: MyVars<img src=x onerror=alert()>

image

  1. Add a variable to your variable set, can be anything you want

image

  1. Add your variable set to an existing or new project

image

  1. View "All Variables" on your project

image

  1. XSS payload fires repeatedly
@michaelnoonan michaelnoonan added kind/bug This issue represents a verified problem we are committed to solving priority (obsolete) This issue has been recognised as a priority and should be addressed as soon as possible labels Nov 14, 2017
@michaelnoonan michaelnoonan added this to the 3.13.7 milestone Nov 14, 2017
@michaelnoonan
Copy link
Contributor Author

michaelnoonan commented Nov 14, 2017

Release Note: Fixed a XSS vulnerability with the All Variables Tab (CVE-2017-16810)

@michaelnoonan
Copy link
Contributor Author

CVE-2017-16810

@lock
Copy link

lock bot commented Nov 24, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug This issue represents a verified problem we are committed to solving priority (obsolete) This issue has been recognised as a priority and should be addressed as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants