invalid memory access error in mixed cluster

Description

In mixed cluster, when one of the nodes supports collections, it is possible that the library would interpret standalone buffer that stores header with key and updated collection id.

reproduction steps

1. setup two node cluster with version 6.6-stable
2. run another node with version 7.1-stable
3. join 7.1-stable with the rest
4. find a key that assigned to one of the vbuckets on 7.1-stable (cbc-keygen generates list of keys distributed across vbuckets, cbc-hash displays node where the given key is stored)
5. bootstrap libcouchbase using address of the 7.1-stable
6. execute kv operation using the key found previously

observed behavior

the application terminated because of illegal memory access

expected behavior

the application completes without any errors

Environment

None

Gerrit Reviews

None

Release Notes Description

None

Activity

Show:

CB robot March 28, 2024 at 5:46 AM

Build couchbase-server-7.2.5-7575 contains libcouchbase commit 3e21d89 with commit message:
: fix memory management for collection id prefix

CB robot March 28, 2024 at 5:46 AM

Build couchbase-server-7.2.5-7575 contains libcouchbase commit 6a1bce4 with commit message:
: fix collection id encoding

CB robot March 28, 2024 at 5:46 AM

Build couchbase-server-7.2.5-7575 contains libcouchbase commit 25637cf with commit message:
: fix invalid memory access when patching collection id

CB robot December 23, 2023 at 1:36 AM

Build capella-analytics-1.0.0-1179 contains libcouchbase commit 3e21d89 with commit message:
: fix memory management for collection id prefix

CB robot December 23, 2023 at 1:36 AM

Build capella-analytics-1.0.0-1179 contains libcouchbase commit 6a1bce4 with commit message:
: fix collection id encoding

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Fix versions

Sprint

Story Points

Components

Reporter

Affects versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created August 30, 2023 at 7:46 PM
Updated March 28, 2024 at 5:46 AM
Resolved September 5, 2023 at 4:27 PM
Instabug