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

bridge networking mode allows ARP spoofing #10568

Closed
shoenig opened this issue May 11, 2021 · 2 comments
Closed

bridge networking mode allows ARP spoofing #10568

shoenig opened this issue May 11, 2021 · 2 comments

Comments

@shoenig
Copy link
Member

shoenig commented May 11, 2021

A vulnerability was discovered in Nomad and Nomad Enterprise (“Nomad”) wherein processes launched by the docker, exec, and java task drivers that make use of Nomad's bridge networking mode can perform ARP spoofing attacks against other tasks on the same node. Specifically, tasks making use of bridge networking are susceptible to other tasks on the same node performing DoS and MITM attacks due to the default enablement of the CAP_NET_RAW Linux capability by these task drivers. This affects all known versions of Nomad. The patch applies to Nomad clients running docker, exec, or java task drivers on Linux with tasks making use of bridge networking mode. Third-party driver plugins that use the shared library code may be similarly affected.

The issue is identified publicly as CVE-2021-32575.

The implemented fix is to no longer enable CAP_NET_RAW by default. Note that this will cause applications which make use of ICMP packets no longer work (e.g. ping). Previous behavior can be restored by setting allow_caps on the docker task driver. A future version of Nomad will implement the same allow_caps configuration for the exec and java task drivers.

@shoenig shoenig changed the title (placeholder) bridge networking mode allows ARP spoofing May 12, 2021
@shoenig
Copy link
Member Author

shoenig commented May 12, 2021

Fixed by #10572

@shoenig shoenig closed this as completed May 12, 2021
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant