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.

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

[Coverity CID :207973] Out-of-bounds access in tests/net/socket/websocket/src/main.c #22438

Closed
zephyrbot opened this issue Feb 3, 2020 · 1 comment
Assignees
Labels
area: Networking bug The issue is a bug, or the PR is fixing a bug Coverity A Coverity detected issue or its fix priority: low Low impact/importance bug

Comments

@zephyrbot
Copy link
Collaborator

Static code scan issues found in file:

https://github.com/zephyrproject-rtos/zephyr/tree/a3e89e84a801d9bc048b0ee2177f0fb11d1a925a/tests/net/socket/websocket/src/main.c#L314

Category: Memory - corruptions
Function: verify_sent_and_received_msg
Component: Tests
CID: 207973

Details:

308                                     total_read,
309                         msg->msg_iov[1].iov_len - total_read,
310                         &ctx, &msg_type, &remaining,
311                         recv_buf, sizeof(recv_buf));
312             zassert_true(ret > 0, "Cannot read data (%d)", ret);
313    
>>>     CID 207973:  Memory - corruptions  (OVERRUN)
>>>     Overrunning array "recv_buf" of 1163 bytes by passing it to a function which accesses it at byte offset 4294967284 using argument "ret" (which evaluates to 4294967285). [Note: The source code implementation of the function has been overridden by a builtin model.]
314             if (memcmp(recv_buf, lorem_ipsum + total_read, ret) != 0) {
315                 LOG_HEXDUMP_ERR(lorem_ipsum + total_read, ret,
316                         "Received message should be");
317                 LOG_HEXDUMP_ERR(recv_buf, ret, "but it was instead");
318                 zassert_true(false, "Invalid received message "
319                          "after %d bytes", total_read);

Please fix or provide comments in coverity using the link:

https://scan9.coverity.com/reports.htm#v32951/p12996.

Note: This issue was created automatically. Priority was set based on classification
of the file affected and the impact field in coverity. Assignees were set using the CODEOWNERS file.

@zephyrbot zephyrbot added bug The issue is a bug, or the PR is fixing a bug Coverity A Coverity detected issue or its fix priority: low Low impact/importance bug labels Feb 3, 2020
@jukkar
Copy link
Member

jukkar commented Feb 12, 2020

False positive

@jukkar jukkar closed this as completed Feb 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Networking bug The issue is a bug, or the PR is fixing a bug Coverity A Coverity detected issue or its fix priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

4 participants