krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-09-28 07:28:30 +02:00
Code Issues Packages Projects Releases Wiki Activity

Tell users to upgrade to v1.8.3

Browse Source
This commit is contained in:
Mac Chaffee
2024-03-19 13:10:57 -04:00
parent a4d7d33c23
commit 0c87180e91
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/blog/cve-2024-2221-response.md
+5 -5
View File
@@ -32,13 +32,13 @@ filesystem is read-only and authentication is enabled by default. At worst,
the vulnerability could be used by an authenticated user to crash a cluster,
which is already possible, such as by uploading more vectors than can fit in RAM.
Qdrant has addressed the vulnerability in v1.8.0 and above with code that
Qdrant has addressed the vulnerability in v1.8.3 and above with code that
restricts file uploads to a folder dedicated to that purpose.
### Action
Check the current version of your Qdrant deployment. Upgrade if your deployment
is not at least v1.8.0.
is not at least v1.8.3.
To confirm the version of your Qdrant deployment in the cloud or on your local
or cloud system, run an API GET call, as described in the [Qdrant Quickstart
@@ -51,7 +51,7 @@ guide.
#### If you use the Qdrant container or binary
Upgrade your deployment. Run the commands in the applicable section of the
Upgrade your deployment. Run the commands in the applicable section of the
[Qdrant Installation](https://qdrant.tech/documentation/guides/installation/)
guide. The default commands automatically pull the latest version of Qdrant.
@@ -59,8 +59,8 @@ guide. The default commands automatically pull the latest version of Qdrant.
If you’ve set up Qdrant on kubernetes using a helm chart, follow the README in
the [qdrant-helm](https://github.com/qdrant/qdrant-helm/tree/main?tab=readme-ov-file#upgrading) repository.
Make sure applicable configuration files point to version v1.8.0 or above.
Make sure applicable configuration files point to version v1.8.3 or above.
#### If you use the Qdrant cloud
#### If you use the Qdrant cloud
No action is required. This vulnerability does not materially affect you. However, we suggest that you upgrade your cloud deployment to the latest version.