Please provide a test case clearly showing the bug in the upstream project.
Calling memset() would be incorrect in this case even if you were concerned about a NULL character ( i.e. the minimal change would be to insert a NULL character in the buffer after looked at the length of the returned string from memcached_response()... but you don't have to do that because it is already done for you ). I mentioned the error path only because in that path there is no guarantee that a NULL would be added to the buffer, but then the buffer passed to memcached_response() goes unused. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573594 Title: Missing null termination in PROTOCOL_BINARY_CMD_SASL_LIST_MECHS response handling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmemcached/+bug/1573594/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
