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

Vulnerability issues: Insecure Path Attribute #4887

Open
9 tasks
mukulk2020 opened this issue Mar 15, 2021 · 0 comments
Open
9 tasks

Vulnerability issues: Insecure Path Attribute #4887

mukulk2020 opened this issue Mar 15, 2021 · 0 comments
Labels
community Community Raised Issue

Comments

@mukulk2020
Copy link

mukulk2020 commented Mar 15, 2021

Stratos Version

Stratos 4.4.0

Frontend Deployment type

  • Cloud Foundry Application (cf push)
  • Kubernetes, using a helm chart
  • Docker, single container deploying all components
  • npm run start
  • Other (please specify below)

Backend (Jet Stream) Deployment type

  • Cloud Foundry Application (cf push)
  • Kubernetes, using a helm chart
  • Docker, single container deploying all components
  • Other (please specify below)

Expected behaviour

PATH should be set to "path=/application name/" and not "path=/".
If the path attribute is set to the web server root "/"directory, then the application along with the hosting web server becomes vulnerable to multiple attacks.

Actual behaviour

It is showing path=/ . and there is no option to change this .

Steps to reproduce the behavior

Log output covering before error and any error statements


Insert log hereCopy

image

Detailed Description

The URL path that the cookie is valid for can be specified. If the domain and path match, then the cookie will be sent in the request. Just as with the domain attribute, if the path attribute is set too loosely, then it could leave the application vulnerable to attacks by other applications on the same server. For example, if the path attribute was set to the web server root "/", then the application cookies will be sent toevery application within the same domain.

Context

Possible Implementation

@richard-cox richard-cox added the community Community Raised Issue label Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Community Raised Issue
Projects
None yet
Development

No branches or pull requests

2 participants