[
https://issues.apache.org/jira/browse/PROTON-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16974332#comment-16974332
]
ASF subversion and git services commented on PROTON-2136:
---------------------------------------------------------
Commit 776b1febebe26447346e534e36c91420b6b15395 in qpid-proton's branch
refs/heads/master from Jiri Danek
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=776b1fe ]
PROTON-2136 Fix fuzz-connection-driver to be tolerant of NULL input buffer
> fuzz-connection-driver.c exits with 1 when the engine stops accepting
> additional input
> --------------------------------------------------------------------------------------
>
> Key: PROTON-2136
> URL: https://issues.apache.org/jira/browse/PROTON-2136
> Project: Qpid Proton
> Issue Type: Test
> Components: proton-c
> Affects Versions: proton-c-0.29.0
> Reporter: Jiri Daněk
> Assignee: Jiri Daněk
> Priority: Major
>
> {noformat}
> size_t fcd_read(pn_connection_driver_t *driver, uint8_t **data, size_t *size)
> {
> pn_rwbytes_t buf = pn_connection_driver_read_buffer(driver);
> size_t s = (*size < buf.size) ? *size : buf.size;
> if (buf.start == NULL) {
> exit(1);
> }
> {noformat}
> The engine offers a null buffer for further input. AFAIK that is legit,
> because it is just that the "socket" was closed for further input, after
> reading the invalid header.
> The fuzz target should just return peacefully at this point and not crash.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
