[GHSA-6q8m-42qq-64r7] Imperative CLI vulnerable to Command Injection - #1744
Closed
MarkAckert wants to merge 1 commit into
Closed
[GHSA-6q8m-42qq-64r7] Imperative CLI vulnerable to Command Injection#1744MarkAckert wants to merge 1 commit into
MarkAckert wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
MarkAckert/advisory-improvement-1744
March 2, 2023 14:54
Author
|
There is still a minor error in this PR, so I will close it and open a new one. |
Contributor
|
@MarkAckert Thank you for letting me know there's a new PR coming! I was just checking PRs 900 and 902 against the commit histories for v4.18.11 and v5.7.2 and will keep an eye out for the new info. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
Comments
I am part of the team that submitted the CVE Request. Due to confusion in communicating versioning, this advisory appears to be incorrect. We marked the CVE as impacting Zowe versions < 1.28.2 or < 2.5.0 which is understood by many of our consumers, but not by automation. We'll fix this going forward. The actual Imperative versions affected are < 4.18.10 or >= 5.0.0, < 5.7.1, and the PRs which fixed the issue were added to the references section. As for my authenticity, I am a Zowe Organization Owner/Administrator and Zowe CLI Squad Member (which owns the Imperative framework). I can provide additional information to verify my authenticity if required, please let me know if that's the case.