CVE-2025-0679

4.3 MEDIUM

📋 TL;DR

This vulnerability in GitLab CE/EE allows unauthorized users to view full email addresses that should be partially obscured under certain conditions. It affects all GitLab instances running vulnerable versions, potentially exposing user email addresses that should be protected.

💻 Affected Systems

Products:
  • GitLab Community Edition
  • GitLab Enterprise Edition
Versions: 17.1 to 17.10.6, 17.11 to 17.11.2, 18.0 to 18.0.0
Operating Systems: All supported platforms
Default Config Vulnerable: ⚠️ Yes
Notes: Affects all deployments of vulnerable versions regardless of configuration.

📦 What is this software?

Gitlab by Gitlab

GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...

Learn more about Gitlab →

Gitlab by Gitlab

GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...

Learn more about Gitlab →

Gitlab by Gitlab

GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...

Learn more about Gitlab →

Gitlab by Gitlab

GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...

Learn more about Gitlab →

Gitlab by Gitlab

GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...

Learn more about Gitlab →

Gitlab by Gitlab

GitLab is a complete DevOps platform providing source code management, CI/CD pipelines, security scanning, container registry, and collaboration tools used by millions of developers and thousands of enterprises worldwide. As both a cloud-hosted SaaS offering (GitLab.com) and self-managed software, G...

Learn more about Gitlab →

⚠️ Risk & Real-World Impact

🔴

Worst Case

Mass exposure of user email addresses leading to targeted phishing campaigns, spam, or identity correlation attacks against GitLab users.

🟠

Likely Case

Limited exposure of some user email addresses that should have been obscured, potentially violating privacy expectations.

🟢

If Mitigated

Minimal impact if proper access controls and monitoring are in place, though privacy violation still occurs.

🌐 Internet-Facing: MEDIUM
🏢 Internal Only: LOW

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

The vulnerability requires specific conditions but is accessible to unauthenticated users when those conditions are met.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 17.10.7, 17.11.3, or 18.0.1

Vendor Advisory: https://gitlab.com/gitlab-org/gitlab/-/issues/514751

Restart Required: Yes

Instructions:

1. Backup your GitLab instance. 2. Update to GitLab 17.10.7, 17.11.3, or 18.0.1 using your preferred update method. 3. Restart GitLab services. 4. Verify the update was successful.

🔧 Temporary Workarounds

Restrict public access

all

Limit GitLab instance access to authorized users only while awaiting patch

# Configure firewall rules or access controls to restrict GitLab access

🧯 If You Can't Patch

  • Implement strict access controls to limit who can access the GitLab instance
  • Monitor logs for unusual access patterns to user profile or email-related endpoints

🔍 How to Verify

Check if Vulnerable:

Check your GitLab version against affected ranges: 17.1-17.10.6, 17.11-17.11.2, or 18.0-18.0.0

Check Version:

sudo gitlab-rake gitlab:env:info | grep 'Version:'

Verify Fix Applied:

Confirm GitLab version is 17.10.7, 17.11.3, or 18.0.1 or higher

📡 Detection & Monitoring

Log Indicators:

  • Unusual access patterns to user profile endpoints by unauthenticated users
  • Multiple failed authentication attempts followed by profile viewing

Network Indicators:

  • Unusual traffic to user-related API endpoints from unauthenticated sources

SIEM Query:

source="gitlab" AND (uri_path="/api/v4/user" OR uri_path="/users/*") AND http_status=200 AND user="-"

🔗 References

📤 Share & Export