You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since composer/packagist@86244a3 here in #10582 composers global --no-ansi switch does not work properly any longer for the binary sequence that was introduced by that change.
It looks like composer passes this information unchecked and unfiltered into the users shell.
The text was updated successfully, but these errors were encountered:
@Seldaek: Thanks for taking care. While stumbling over it, it is perhaps useful to refuse using any message if it contains one or more NUL bytes - and perhaps everything of C0 (apart what you need for colors as not possible to strip) - just to lower the injection potential into the users shell. You perhaps already thought about it.
Let's be honest, if a repository wants to mess with you, it can serve you URLs to packages with malware in them.. so I think we can assume some amount of good-will/trust here.
Okay, let's be honest: A NUL byte / C0 check would also not turn this into a malware shield. I had more my own terminal messes in mind when injecting control characters than anything else. More error correction than anything else.
So better make the regex pattern filtering out actual ANSI sequences first of all - if anything.
Since composer/packagist@86244a3 here in #10582 composers global
--no-ansi
switch does not work properly any longer for the binary sequence that was introduced by that change.It looks like composer passes this information unchecked and unfiltered into the users shell.
The text was updated successfully, but these errors were encountered: