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

Bug: Potential Link Executor Selection #56

Closed
d3vco opened this issue Jun 17, 2024 · 0 comments · Fixed by #57
Closed

Bug: Potential Link Executor Selection #56

d3vco opened this issue Jun 17, 2024 · 0 comments · Fixed by #57
Assignees
Labels
bug Something isn't working good write up

Comments

@d3vco
Copy link
Contributor

d3vco commented Jun 17, 2024

Description

This issue is identical to Caldera v4.2's issue #2842.

When adding a Potential Link to an operation, links are matched on executor name only. This has the potential of selecting an executor platform that does not match the agent's platform.

To Reproduce

Steps to reproduce the behavior:

  1. Fresh install Caldera v5 with stockpile plugin included
  2. Deploy an agent to a linux platform
  3. Start a new operation
  4. Open the add potential link modal
  5. Select the linux agent
  6. Select the "sh" executor
  7. Search for and select the "Parse ssh config" ability
  8. Observe that the command populated on the next screen is the darwin specific command (pip install stormssh && storm list)

Expected Behavior

Following the steps above, the pre-populated command should be the linux command: pip install -q stormssh 2> /dev/null && storm list | sed 's/\x1b\[[0-9;]*m//g'

Fix

Bugfix created. Will submit PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good write up
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants