*read-eval* false? #82
You're right, but this bug has been fixed. You're looking at an old repository. Here's the latest code:
Thanks for the response.
I apologize for the false positive. (I'm not sure how I ended up reading a
old version of the code).
…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At https://github.com/mmcgrana/ring/blob/master/ring-core/src/ring/middleware/session/cookie.clj#L92
should there be a
(binding [read-eval false] ) ?
Otherwise, it seems -- suppose some other vulnerability allowed the AES key to leak -- then we suddenly have the situation where the client can do arbitrary code execution by read macros?