Facebook  Twitter  Google +  Linkedin


Warning: file_get_contents(): https:// wrapper is disabled in the server configuration by allow_url_fopen=0 in /home/lwegabab/public_html/old/plugins/content/al_facebook_comments/al_facebook_comments.php on line 516

Warning: file_get_contents(https://api.facebook.com/restserver.php?method=links.getStats&urls=https://www.old.yourictmagazine.com/security/886-google-project-zero-gpz-finds-security-flaw-in-github): Failed to open stream: no suitable wrapper could be found in /home/lwegabab/public_html/old/plugins/content/al_facebook_comments/al_facebook_comments.php on line 516

Warning: Undefined array key 1 in /home/lwegabab/public_html/old/plugins/content/al_facebook_comments/al_facebook_comments.php on line 521

Google Project Zero (GPZ) finds security flaw in GitHubGoogle's Project Zero in July found a security flaw in Microsoft's GitHub. The bug relates to GitHub Actions' workflow commands and is described as being high severity.
As the runner process parses every line printed to STDOUT looking for workflow commands, every GitHub action that prints untrusted content as part of its execution is vulnerable. In most cases, the ability to set arbitrary environment variables results in remote code execution as soon as another workflow is executed,"

GitHub failed to fix the bug as per the standard 90-day disclosure period thus being made public. Since 2014 GPZ publishes a vulnerability in a certain vendor's software or Hardware, they always notice the owners before making it public.


However, GitHub in their defence on 1st October made a press release on their blog.
"A moderate security vulnerability has been identified in the GitHub Actions runner that can allow environment variable and path injection in workflows that log untrusted data to STDOUT. This can result in environment variables being introduced or modified without the intention of the workflow author."
see more here Github Blog