Number of incidents affecting GitHub, Bitbucket, Gitlab and Jira is rising
Incidents on major development platforms like GitHub, Bitbucket, GitLab, and Jira are rising, with GitHub up 21% in 2023, highlighting security challenges and the need for better collaboration in DevSecOps.
Read original articleThe number of incidents affecting major development platforms such as GitHub, Bitbucket, GitLab, and Jira has been increasing, posing significant challenges for DevSecOps teams. In 2023, GitHub experienced a 21% rise in incidents, with RepoJacking attacks exposing millions of repositories to vulnerabilities. Bitbucket saw a slight decrease in incidents, while Jira users faced a 50% increase, totaling 75 incidents. GitLab reported that 32% of its incidents impacted service performance, with notable disruptions occurring in June and August. Security vulnerabilities, including critical Remote Code Execution flaws, were prevalent across these platforms. Attackers have increasingly exploited GitHub for malicious purposes, using it to host malware and execute commands covertly. The integration of security into the development process remains a challenge, as developers prioritize speed while security teams focus on vulnerability management. This disconnect can lead to data breaches and operational disruptions, emphasizing the need for a collaborative approach to security in the software development lifecycle.
- Incidents affecting GitHub, Bitbucket, GitLab, and Jira are on the rise, with GitHub seeing a 21% increase in 2023.
- RepoJacking attacks have exposed millions of repositories on GitHub to vulnerabilities.
- Jira users experienced a 50% increase in incidents, while GitLab reported significant service performance issues.
- Attackers are using GitHub to host malware and execute commands, complicating threat detection.
- The integration of security in DevSecOps processes remains a challenge due to differing priorities between developers and security teams.
Related
Leaked admin access token to Python, PyPI, and PSF GitHub repos
The JFrog Security Research team discovered a leaked admin access token for Python repositories on GitHub. PyPI promptly revoked the token, preventing a supply chain attack. Emphasizes the importance of scanning binaries for security.
"GitHub" Is Starting to Feel Like Legacy Software
GitHub faces criticism for performance decline and feature issues like blame view rendering large files. Users find navigation challenging and core features neglected despite modernization efforts. Users consider exploring alternative platforms.
Nation-State Actors Targeting Software Supply Chain via GitHub [2023)
GitHub warns of Lazarus Group, linked to North Korea, targeting cryptocurrency, gambling, and cybersecurity sectors via social engineering. Group aims to breach software supply chains for financial gain. Panther Labs offers security workshop.
GitHub Actions Outage
GitHub is facing issues with actions and jobs, working to resolve by failing over to another region. Users can subscribe for updates via email, text, Slack, or webhook notifications for ongoing incident information.
Anyone Can Access Deleted and Private Repository Data on GitHub
GitHub's architecture allows access to data from deleted and private repositories, posing security risks. The Cross Fork Object Reference vulnerability enables retrieval of sensitive information even after deletion, necessitating user vigilance.
If the business wants to dictate deadlines, the business is responsible for security.
Edit: I should say development team to include qa, but we don’t have those anymore at most places.
This is the best that most separate security teams do, too.
In all fairness, the "DevOps" part of things can manage deploys in ways to minimize exposure. But most teams that I've seen revert to manual "process" whenever something unusual occurs, so forget about the ideal automated responses to problems we were promised when we were trying to automate sysadmins out of their jobs. There are several layers of broken here that we're not allowed to talk about.
I've resisted this, because I know that I can sleep peacefully at night when the inevitable monthly "GitLab Critical Patch Release" email comes.
Related
Leaked admin access token to Python, PyPI, and PSF GitHub repos
The JFrog Security Research team discovered a leaked admin access token for Python repositories on GitHub. PyPI promptly revoked the token, preventing a supply chain attack. Emphasizes the importance of scanning binaries for security.
"GitHub" Is Starting to Feel Like Legacy Software
GitHub faces criticism for performance decline and feature issues like blame view rendering large files. Users find navigation challenging and core features neglected despite modernization efforts. Users consider exploring alternative platforms.
Nation-State Actors Targeting Software Supply Chain via GitHub [2023)
GitHub warns of Lazarus Group, linked to North Korea, targeting cryptocurrency, gambling, and cybersecurity sectors via social engineering. Group aims to breach software supply chains for financial gain. Panther Labs offers security workshop.
GitHub Actions Outage
GitHub is facing issues with actions and jobs, working to resolve by failing over to another region. Users can subscribe for updates via email, text, Slack, or webhook notifications for ongoing incident information.
Anyone Can Access Deleted and Private Repository Data on GitHub
GitHub's architecture allows access to data from deleted and private repositories, posing security risks. The Cross Fork Object Reference vulnerability enables retrieval of sensitive information even after deletion, necessitating user vigilance.