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.

Sign up for GitHub

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

Jump to bottom

Info result parsing #7298

Closed
aafemt opened this issue Sep 8, 2022 · 1 comment
Closed

Info result parsing #7298

aafemt opened this issue Sep 8, 2022 · 1 comment
Assignees
@AlexPeshkoff
Labels
affect-version: 3.0.10 affect-version: 4.0.2 affect-version: 5.0 Initial fix-version: 3.0.11 fix-version: 4.0.3 fix-version: 5.0 Beta 1 type: bug

Comments

@aafemt
Copy link
Contributor

aafemt commented Sep 8, 2022

Since ClumpletReader supports this buffer format, every piece of Firebird code should use it to parse result of getInfo() calls. It should fix multiple BOFs in handling of isc_info_truncated item.
@AlexPeshkoff AlexPeshkoff self-assigned this Sep 14, 2022
@AlexPeshkoff AlexPeshkoff reopened this Sep 28, 2022
AlexPeshkoff added a commit that referenced this issue Sep 30, 2022
@AlexPeshkoff
Postfix for #7298: Info result parsing; avoid buffer overflow when pr…
9c703c0 
…ocessing isc_info_error
AlexPeshkoff added a commit that referenced this issue Sep 30, 2022
@AlexPeshkoff
Backported fix for #7298: Info result parsing
4d0e5e0
AlexPeshkoff added a commit that referenced this issue Sep 30, 2022
@AlexPeshkoff
Backported fix for #7298: Info result parsing
b40006d
@AlexPeshkoff
Copy link
Member

Just small notice before closing - not only isc_info_truncated was affected, isc_info_end handling in some cases was also buggy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlexPeshkoff AlexPeshkoff

Labels
affect-version: 3.0.10 affect-version: 4.0.2 affect-version: 5.0 Initial fix-version: 3.0.11 fix-version: 4.0.3 fix-version: 5.0 Beta 1 type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AlexPeshkoff @aafemt