You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@daffodil.apache.org by "Josh Adams (Jira)" <ji...@apache.org> on 2020/10/14 20:08:00 UTC

[jira] [Updated] (DAFFODIL-2411) Investigate potential Integer overflows

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

Josh Adams updated DAFFODIL-2411:
---------------------------------
    Fix Version/s:     (was: 3.0.0)

> Investigate potential Integer overflows
> ---------------------------------------
>
>                 Key: DAFFODIL-2411
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2411
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End
>    Affects Versions: 3.0.0
>            Reporter: Josh Adams
>            Priority: Minor
>
> There are a number of places where we are getting a length of an element or an array that could potentially cause an integer overflow to occur.
> For example, all the binary number parsers have a getBitLength funciton that returns an int. It is unlikely for a binary number to have such a large length that it overflows, but if there were bad data or a bad dfdl:length expression, it could definately happen.
> Currently there are calls in many different places that would need range checks to prevent this, so it may require some re-architecture to provide a clean solution.



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