You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CVE-2022-24687 appears to be a case of the known issue where the vulnerability is really in the Consul server— not the API client that we're using— but scanners conflate the two due to how Hashicorp's code is organized. So, even though (as we understand it), there is no vulnerability in v1.11.0 of the API client, there is one in v1.11.0 of the server, so in order to stop getting warnings we must update the API client to a newer version. It looks like such a version is available, so we will release a patch ASAP.
The text was updated successfully, but these errors were encountered:
(This issue is an FYI update from LaunchDarkly)
CVE-2022-24687 appears to be a case of the known issue where the vulnerability is really in the Consul server— not the API client that we're using— but scanners conflate the two due to how Hashicorp's code is organized. So, even though (as we understand it), there is no vulnerability in v1.11.0 of the API client, there is one in v1.11.0 of the server, so in order to stop getting warnings we must update the API client to a newer version. It looks like such a version is available, so we will release a patch ASAP.
The text was updated successfully, but these errors were encountered: