Impact
What kind of vulnerability is it? Who is impacted?
An unauthenticated attacker can exploit this vulnerability to bypass all authentication mechanisms in the Milvus Proxy component, gaining full administrative access to the Milvus cluster.
This grants the attacker the ability to read, modify, or delete data, and to perform privileged administrative operations such as database or collection management.
All users running affected Milvus versions are strongly advised to upgrade immediately.
Patches
Has the problem been patched? What versions should users upgrade to?
This issue has been fixed in the following versions:
• Milvus 2.4.24
• Milvus 2.5.21
• Milvus 2.6.5
Users should upgrade to these patched versions or later to mitigate the vulnerability.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
If immediate upgrade is not possible, a temporary mitigation can be applied by removing the sourceID header from all incoming requests at the gateway, API gateway, or load balancer level before they reach the Milvus Proxy.
This prevents attackers from exploiting the authentication bypass behavior.
References
Are there any links users can visit to find out more?
The following pull requests contain the fixes for the affected Milvus branches:
• Fix for 2.4 branch
• Fix for 2.5 branch
• Fix for 2.6 branch
Special thanks to the Volcengine Milvus team at ByteDance([email protected]) for responsibly discovering, reporting, and coordinating the disclosure of this critical authentication bypass vulnerability with the Milvus maintainers.
Impact
What kind of vulnerability is it? Who is impacted?
An unauthenticated attacker can exploit this vulnerability to bypass all authentication mechanisms in the Milvus Proxy component, gaining full administrative access to the Milvus cluster.
This grants the attacker the ability to read, modify, or delete data, and to perform privileged administrative operations such as database or collection management.
All users running affected Milvus versions are strongly advised to upgrade immediately.
Patches
Has the problem been patched? What versions should users upgrade to?
This issue has been fixed in the following versions:
• Milvus 2.4.24
• Milvus 2.5.21
• Milvus 2.6.5
Users should upgrade to these patched versions or later to mitigate the vulnerability.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
If immediate upgrade is not possible, a temporary mitigation can be applied by removing the sourceID header from all incoming requests at the gateway, API gateway, or load balancer level before they reach the Milvus Proxy.
This prevents attackers from exploiting the authentication bypass behavior.
References
Are there any links users can visit to find out more?
The following pull requests contain the fixes for the affected Milvus branches:
• Fix for 2.4 branch
• Fix for 2.5 branch
• Fix for 2.6 branch
Special thanks to the Volcengine Milvus team at ByteDance([email protected]) for responsibly discovering, reporting, and coordinating the disclosure of this critical authentication bypass vulnerability with the Milvus maintainers.