You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Micah Kornfield (Jira)" <ji...@apache.org> on 2021/02/10 05:05:00 UTC

[jira] [Resolved] (ARROW-11559) [C++] Improve flatbuffers verification limits

     [ https://issues.apache.org/jira/browse/ARROW-11559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Micah Kornfield resolved ARROW-11559.
-------------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Issue resolved by pull request 9447
[https://github.com/apache/arrow/pull/9447]

> [C++] Improve flatbuffers verification limits
> ---------------------------------------------
>
>                 Key: ARROW-11559
>                 URL: https://issues.apache.org/jira/browse/ARROW-11559
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Antoine Pitrou
>            Assignee: Antoine Pitrou
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> See discussion in [https://github.com/apache/arrow/pull/9349#issuecomment-775295349] :
> Flatbuffers is able to encode a virtually unbounded of schema fields in a small buffer size. Verifying that many fields with the Flatbuffers verifier seems to result in potentially unlimited verification times, which is a denial of service risk.
> The way to mitigate this risk is to pass an appropriate max_tables and/or max_depth limit to the Flatbuffers verifier.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)