[Bug]: CVEs of milvus-etcd

[weiZhenkun]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version: 2.4.5

Current Behavior

Can we update to the latest version of milvus-etcd?

Image	Total	CRITICAL&HIGH	CVE detail
docker.io/milvusdb/etcd:3.5.5-r4	203	54	(UNKNOWN: 0, LOW: 78, MEDIUM: 74, HIGH: 49, CRITICAL: 2)
docker.io/bitnami/etcd:3.5.14	91	4	(UNKNOWN: 0, LOW: 66, MEDIUM: 20, HIGH: 4, CRITICAL: 1)

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

[yanliang567]

/assign @LoveEachDay
I think we has some plans for this, please help to share more info
/unassign

[weiZhenkun]

@LoveEachDay please share the info, thanks.

[LoveEachDay]

@weiZhenkun We are testing etcd 3.5.14 inhouse, and will release alongside the next milvus upgrade if everything is ok.

[weiZhenkun]

@LoveEachDay Can we also upgrade the base image from Debian 11 to Debian 12?

• Debian's fixes for Debian 11 are not very timely, and there are still many CVEs. Debian 12 (bookworm) has fewer CVEs now and the CVEs of it will be fixed relatively timely.

• Debian 11 will not fullly support on August 14th, 2024.

[xiaofan-luan]

we are targeting to upgrade etcd to 3.5.14 in 2.4.7 right? @LoveEachDay