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

Fetching from a scrollable cursor may overwrite user-specified buffer and corrupt memory #7056

Closed
dyemanov opened this issue Dec 1, 2021 · 3 comments

Comments

@dyemanov
Copy link
Member

dyemanov commented Dec 1, 2021

Every fetch from a scrollable cursor returns 2-8 bytes longer message than the client expects. Sometimes this may be harmless, but sometimes it may corrupt application memory and thus cause various crashes.

@dyemanov dyemanov self-assigned this Dec 1, 2021
dyemanov added a commit that referenced this issue Dec 6, 2021
…cified buffer and corrupt memory) and #7057 (Client-side positioned updates work wrongly with scrollable cursors) with a single shot
@pavel-zotov
Copy link

Test will be added after migration to pytest/firebird-driver framework.

@ilya071294
Copy link
Collaborator

Will FB3 be fixed?

@dyemanov
Copy link
Member Author

dyemanov commented Feb 5, 2022

It requires more changes for backporting, thus was postponed. But if there's a demand to have this fix in v3, I will do it during this weekend.

dyemanov added a commit that referenced this issue Feb 8, 2022
…cified buffer and corrupt memory) and #7057 (Client-side positioned updates work wrongly with scrollable cursors) with a single shot
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment