Description
Various IDs are used in Mesos, some assigned by the master (AgentID, FrameworkID, etc) and some created by the frameworks (TaskID, ExecutorID etc).
The master does sufficient validation on the IDs supplied by the frameworks and the agent currently just trusts that the IDs are valid because they have been validated.
The problem is that currently any entity can spoof as the master to inject certain actions on the agent which can be executed as "root" and inflict harm on the system. The "right" long term fix is of course to prevent this from happening but as a short-term defensive measure we can insert some hard CHECKs on the validity of the IDs in the agent code paths.
Attachments
Issue Links
- is related to
-
MESOS-6862 Replace os::system usages to reduce the risk of command injection.
-
- Resolved
-
-
MESOS-7086 Tighten up rules on IDs used in Mesos
-
- Open
-