Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrade nats-server #1082

Conversation

AbhilashVijayakumar
Copy link

Upgrade NATS Server due to ddos vulnerability :

  • Version 2 prior to 2.2.0
    • 2.0.0 through and including 2.1.9 are vulnerable
  • fixed with nats-io/nats-server commit 423b79440c (2021-03-14)

refer https://advisories.nats.io/CVE/CVE-2021-3127.txt

NATS Server ddos:
 * Version 2 prior to 2.2.0
   + 2.0.0 through and including 2.1.9 are vulnerable
 * fixed with nats-io/nats-server commit 423b79440c (2021-03-14)
@ChrisHines
Copy link
Member

This seems fine to me, but it should be noted that go-kit only uses nats-server in tests. Also, this change will not propagate to to go-kit dependents until we tag a new release and we should check our go.mod for out of date dependencies when we are preparing a new go-kit release anyway.

@sagikazarmark
Copy link
Contributor

Would it make sense to rewrite those tests to use an external nats server instance (similarly to etcd, zookeeper, etc)?

I understand the value of self-contained tests, but this could make the dependency graph smaller.

@peterbourgon
Copy link
Member

@AbhilashVijayakumar Ping :) Can you fix the tests, please?

@peterbourgon
Copy link
Member

#1095

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants