Skip to content

BUGFIX: Avoid insecure composer/composer versions #3366

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

Merged
merged 1 commit into from
Jun 11, 2024

Conversation

kdambekalns
Copy link
Member

This adjusts the dependency to ~2.2.24 || ^2.7.7 to avoid versions vulnerable to multiple command injections via malicious branch names.

More details in:

Checklist

  • Code follows the PSR-2 coding style
  • Tests have been created, run and adjusted as needed
  • The PR is created against the lowest maintained branch
  • Reviewer - PR Title is brief but complete and starts with FEATURE|TASK|BUGFIX
  • Reviewer - The first section explains the change briefly for change-logs
  • Reviewer - Breaking Changes are marked with !!! and have upgrade-instructions

This adjusts the dependency to `~2.2.24 || ^2.7.7` to avoid versions
vulnerable to multiple command injections via malicious branch names.
@kdambekalns kdambekalns requested review from fcool, kitsunet and albe June 11, 2024 10:19
@kdambekalns kdambekalns self-assigned this Jun 11, 2024
@kdambekalns kdambekalns merged commit 43f7de3 into neos:7.3 Jun 11, 2024
8 of 9 checks passed
@kdambekalns kdambekalns deleted the bugfix/composer-security-fix branch June 11, 2024 10:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants