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

In-memory cache of byte array is vulnerable for external modifications #57

Closed
tujhex opened this issue Mar 25, 2019 · 3 comments
Closed
Assignees

Comments

@tujhex
Copy link

tujhex commented Mar 25, 2019

Hi. When write/read byte arrays, lib uses in-memory cache. But if you get those array, and modify it - cache also modifies, because you have the same reference.
I encountered that when I tried to clear some fetched data with new Random().nextBytes(data) after usage.

@iamironz iamironz self-assigned this May 14, 2019
@iamironz
Copy link
Contributor

Hi! Thank you for submitting, I'll fix this issue ASAP.

@otopba
Copy link

otopba commented Jan 10, 2020

@iamironz 14 May 2019 ASAP =) Any updates?

@iamironz
Copy link
Contributor

Already fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants