Possible length extension attack in line:
https://cgit.drupalcode.org/drupalauth4ssp/tree/drupalauth4ssp.module#n69
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | drupalauth4ssp-3020308-4.patch | 1.5 KB | rosk0 |
Possible length extension attack in line:
https://cgit.drupalcode.org/drupalauth4ssp/tree/drupalauth4ssp.module#n69
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | drupalauth4ssp-3020308-4.patch | 1.5 KB | rosk0 |
Comments
Comment #2
daggerhart commentedI'll take a look at this and see what we can do to mitigate.
Comment #3
tom.camp commentedDaggerhart, has there been any progress here?
Comment #4
rosk0Comment #5
larowlanLooks good to me, is consistent with how core does things.
Only observation would be - is it worth also using core's hash salt for the salt, so you have the ssp config salt, the private key and the hash salt being used?
Comment #8
rosk0Thanks @larowlan! Unfortunately I noticed your message too late so created a child for your suggestion, not sure if it will make a huge difference though, we still need to access SSP config to get a cookie name.
Crediting @plach for manual testing confirmed here https://github.com/drupalauth/simplesamlphp-module-drupalauth/pull/51#is...