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

Security bug : leak private data of last user #751

Merged
merged 1 commit into from Jun 25, 2014

Conversation

ilinz
Copy link

@ilinz ilinz commented Apr 26, 2014

Current thread does not clear, so the exception thrown by the parseRequest method can leak private data of last user.
Request headers with non-numeric port will cause error by the parseInt method and lead to problems.

Current thread does not clear, so the exception thrown by the parseRequest method can leak private data of last user.
Request headers with non-numeric port will cause error by the parseInt method and lead to problems.
@cloudbees-pull-request-builder

play-1-3-x-pull-requests #192 SUCCESS
This pull request looks good

@Notalifeform
Copy link
Contributor

hi @ilinz
Could you create a lighthouse ticket?
I'd be happy to merge it.

regards,

Robert

@ilinz
Copy link
Author

ilinz commented Apr 28, 2014

Thanks for your reply. I have sent an email to Guillaume Bort. :)

regards,

@Notalifeform
Copy link
Contributor

@ilinz This is a security issue, but not that sensitive IMHO - also the fact that there is a pull request refering to is means that it is already 'known'. So a normal lighthouse would be fine.

regards,

Robert

pepite added a commit that referenced this pull request Jun 25, 2014
Security bug : leak private data of last user
@pepite pepite merged commit 38b8f92 into playframework:1.2.x Jun 25, 2014
@alexanderkjall
Copy link

Would it be possible to apply for a CVE for this issue? That would greatly simplify for us to track the issue in our organization. And it would also be great if you could publish a list of affected versions somewhere, (or maybe you have and I just can't find it).

@asolntsev
Copy link
Contributor

@alexanderkjall Sorry, I don't understand your question. What exactly should we do? What means "apply for CVE"?

I guess affected version is 1.2.x and all previous versions.

@alexanderkjall
Copy link

Hi, sorry that I maybe came of as a bit aburpt, I didn't manage to find your page with security information (this one https://www.playframework.com/security/vulnerability/20151230-SessionHijack ) and was stressed.

Regarding your question, a CVE is a tracking number for security problems. It's used both as a way to easily identify and talk about security problems, and also there is automated tooling that can notify you about security issues in your dependencies (for example: https://www.owasp.org/index.php/OWASP_Dependency_Check ).

You as a project can apply for CVE's here: https://docs.google.com/forms/d/e/1FAIpQLSeiY7ldJAx-fjU6eSnXDaX5TB--L1ujCQpmGAKnqBSJOcBShw/viewform (link came from here: https://cve.mitre.org/cve/request_id.html ).

Best regards.

@asolntsev
Copy link
Contributor

@alexanderkjall Thank you for the clarification. But this problem existed very long time ago - in Play 1.2.x. This is very old version! Why do you still need it?

@alexanderkjall
Copy link

@asolntsev because i work in an organisation that built itself into a corner and have managed to get out of it T_T.

Applying for a CVE isn't important for me now, but it would be helpful in the future if security problems got logged, since that would enable our automated tooling to detect and alert us.

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

Successfully merging this pull request may close these issues.

None yet

6 participants