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

REMEMBERME cookie sent to Sentry #43

Closed
kgilden opened this issue Feb 10, 2017 · 7 comments
Closed

REMEMBERME cookie sent to Sentry #43

kgilden opened this issue Feb 10, 2017 · 7 comments

Comments

@kgilden
Copy link

kgilden commented Feb 10, 2017

Hey,

Currently the cookie used to store a "remember-me" token is sent to Sentry. Knowing this value lets an adversary impersonate a user. Perhaps this should be sent as filtered out-of-the-box just like PHPSESSID is filtered.

Note that simply filtering the default REMEMBERME cookie does not cut it. The name can be configured (http://symfony.com/doc/current/security/remember_me.html). Best option IMO is to use a compiler pass and grab it from a certain service definition argument. In the compiler pass we would have to figure the "remember-me" service id (it's dynamic I think), find the service and then infer the cookie name from the 3-rd "options" argument. The relevant part in Symfony can be found here.

Cheers,
Kristen

@Jean85
Copy link
Collaborator

Jean85 commented Apr 28, 2017

Since the name of the cookie is part of the Symfony config, it can be easily retrieved from the config as the security.firewalls.*.remember_me.name parameter.

Good to know, are you able to provide a PR?

@kgilden
Copy link
Author

kgilden commented Apr 29, 2017

Yup, in a week or so.

@Jean85 Jean85 added this to the Stable release 1.0 milestone Aug 5, 2017
@Jean85
Copy link
Collaborator

Jean85 commented Aug 8, 2017

Hi @kgilden, are you still available to provide a PR for this issue? I would like to solve this issue before the 1.0 release.

@kgilden
Copy link
Author

kgilden commented Aug 8, 2017

@Jean85 sorry, I'm afraid I don't have the time even though I promised I'd do it initially :/

@Jean85
Copy link
Collaborator

Jean85 commented Aug 8, 2017

Don't worry, I just wanted to know to avoid doing the work twice!

@Jean85
Copy link
Collaborator

Jean85 commented Oct 31, 2017

This is stale. I don't want this to block the new stable release, hence I'm removing this from the milestone.

@Jean85 Jean85 removed this from the Stable release 1.0 milestone Oct 31, 2017
@Jean85
Copy link
Collaborator

Jean85 commented May 6, 2019

Closing this as stale; also, v3 doesn't send it by default, you need to enable the "send PII" option in the PHP SDK.

@Jean85 Jean85 closed this as completed May 6, 2019
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

No branches or pull requests

2 participants