Authentication Bypass Using an Alternate Path or Channel in GitLab
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| GitLab | GitLab | unaffected |
|
Configuration 1 [-]
|
No data.
No data available yet.
Vendor Solution
Upgrade to versions 16.7.6, 16.8.3, 16.9.1 or above.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-17273 | An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.1 before 16.7.6, all versions starting from 16.8 before 16.8.3, all versions starting from 16.9 before 16.9.1. Under some specialized conditions, an LDAP user may be able to reset their password using their verified secondary email address and sign-in using direct authentication with the reset password, bypassing LDAP. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.449% probability within 30 days)
| Link | Providers |
|---|---|
| https://gitlab.com/gitlab-org/gitlab/-/issues/438144 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-284 |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Improper Access Control in GitLab | Authentication Bypass Using an Alternate Path or Channel in GitLab |
| Weaknesses | CWE-288 |