BlogsGitLabAPI Security Vulnerability Research

API Security Vulnerability Research

API Security Vulnerability Research

2
posts
2018–2019

GitLab has evolved its API security by deprecating and removing older API versions (v3) in favor of newer, more secure versions (v4). This ensures that integrations are using the latest security standards and features, reducing potential vulnerabilities and improving overall API robustness. The process involves clear communication and documentation for users to upgrade their integrations, minimizing downtime and ensuring a smooth transition to more secure API endpoints.

2019

Shopping for an admin account via path traversal

11/29/2019

This post details the discovery and exploitation of a path traversal vulnerability in the GitLab Customers Portal's interaction with the GitLab.com API. The vulnerability allowed an attacker to traverse API paths and inject attributes, leading to privilege escalation by promoting regular accounts to admin. The post also outlines the mitigation strategy, which involved enforcing numerical IDs for the `@namespace_id` parameter and implementing additional defense-in-depth measures.

2018

Breaking change: Support for API v3 will be removed June 4

6/1/2018

This post announces the deprecation and upcoming removal of API v3, mandating an upgrade to API v4 for all integrations connected to GitLab.com. It provides a deadline (June 4, 2018) for integrations to be updated to avoid service disruption and a link to documentation for the upgrade process. The removal is scheduled for GitLab 11.0 on June 22, 2018.