Environment-name disclosure via missing endpoint authorization
Published Apr 5, 2023 · Updated Feb 11, 2025
Improper access control in GitLab 13.6 through 15.8.4, 15.9 through 15.9.3, and 15.10.0 allows remote attackers to read restricted environment names. The unfoldered_environment_names action omits the read-environment authorization check and returns names through a group JSON endpoint. No account is required, but the target must contain a public project whose environment visibility is limited to project members; exposure is limited to environment names.
Summary
What happened
Improper access control in GitLab 13.6 through 15.8.4, 15.9 through 15.9.3, and 15.10.0 allows remote attackers to read restricted environment names. The unfoldered_environment_names action omits the read-environment authorization check and returns names through a group JSON endpoint. No account is required, but the target must contain a public project whose environment visibility is limited to project members; exposure is limited to environment names.
The record
- CVE
- CVE-2023-0319
- Published
- Apr 5, 2023
- Updated
- Feb 11, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 5, 2023CVE publishedPublication date reported by the CVE source.
- Feb 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>=13.6, <15.8.5
- Affected versionversion=>=15.10, <15.10.1
- Affected versionversion=>=15.9, <15.9.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Unauthenticated unfoldered_environment_names requestproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo