GitHub user dnwe opened a pull request:

    https://github.com/apache/qpid-proton/pull/76

    PROTON-1249: Safeguard type initialisations.

    In #readValue() for ArrayType, BinaryType, ListType and MapType
    decoding, if the 'count' specified is very large then it is likely to
    trigger an OutOfMemoryException. As these can come from an external data
    source, during the SASL init for example, there is a potential for a
    denial of service. The fix is to throw an IllegalArgumentException if
    the count value is larger than the amount of data available in the
    received bytes.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dnwe/qpid-proton PROTON-1249

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-proton/pull/76.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #76
    
----
commit 0c92828864118517f8d8a23a2801da82852cf36c
Author: Dominic Evans <[email protected]>
Date:   2016-03-18T11:20:23Z

    PROTON-1249: Safeguard type initialisations.
    
    In #readValue() for ArrayType, BinaryType, ListType and MapType
    decoding, if the 'count' specified is very large then it is likely to
    trigger an OutOfMemoryException. As these can come from an external data
    source, during the SASL init for example, there is a potential for a
    denial of service. The fix is to throw an IllegalArgumentException if
    the count value is larger than the amount of data available in the
    received bytes.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to