Skip to content
This repository was archived by the owner on Sep 26, 2024. It is now read-only.

Check for open redirection attacks - #2

Merged
slewis74 merged 3 commits into
masterfrom
bug-crosssite
Nov 14, 2016
Merged

Check for open redirection attacks#2
slewis74 merged 3 commits into
masterfrom
bug-crosssite

Conversation

@slewis74

Copy link
Copy Markdown
Contributor

Added checks for open redirection attacks and updated packages to get latest virtual directory path handling implementation.

…hind a reverse proxy, and provide error messages if the heades aren't being passed through correctly
…so added checks for open redirection attacks
@slewis74 slewis74 changed the title Open redirection attacks Check for open redirection attacks Nov 11, 2016
state = postLoginRedirectTo;

string[] whitelist = null;
if (Debugger.IsAttached)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I feel like this whitelist should be provided by the Octopus Server somehow - it knows which mode it's running in. Here we're kind of doing it "ambiently" by picking up if a Debugger is attached.

Can the Octopus Server provide a "service" which the extensions can query for a whitelist? I feel like this would be less brittle. Especially if we need to allow people to specify their own whitelist as a configuration option.

Actually, that might not be a bad idea either, make it a configuration option which our scripts fill in with localhost

@slewis74
slewis74 merged commit 85168b3 into master Nov 14, 2016
@slewis74
slewis74 deleted the bug-crosssite branch November 14, 2016 02:16
tothegills pushed a commit that referenced this pull request Mar 31, 2023
Updating Repo from upstream changes
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants