See also #29714 and https://groups.google.com/g/django-
developers/c/H5hJxpwYFcw.
A quick github search yielded multiple occasions where session IDs ended
up in public bug reports:
https://github.com/GibbsConsulting/django-plotly-dash/issues/376
https://github.com/ome/omero-mapr/issues/42
https://github.com/jhelbert/great_teaching_network/issues/220
https://github.com/dzone/osqa/issues/355
I am sure you could find many more. This could potentially be exploited
by automatically searching for such requests and hijacking the associated
accounts.
--
Ticket URL: <https://code.djangoproject.com/ticket/33606>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/33606#comment:1>
* owner: (none) => Tobias Bengfort
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/33606#comment:2>
* needs_docs: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/33606#comment:3>
* needs_docs: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/33606#comment:4>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/33606#comment:5>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"350455b666a289d336fca770578887ce51f1aebe" 350455b6]:
{{{
#!CommitTicketReference repository=""
revision="350455b666a289d336fca770578887ce51f1aebe"
Fixed #33606 -- Cleansed sessionid cookie in error reports.
Co-authored-by: Simon Charette <chare...@gmail.com>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33606#comment:6>