CVE-2023-3509: Group member with sub-maintainer role can change title of shared private deploy keys

Published Feb 21, 2024
·
Updated

An issue has been discovered in GitLab affecting all versions before 16.7.6, all versions starting from 16.8 before 16.8.3, all versions starting from 16.9 before 16.9.1. It was possible for group members with sub-maintainer role to change the title of privately accessible deploy keys associated with projects in the group.

Affected Software

4 affected componentsFixes available
GitLab GitLab<=16.7.6
GitLab GitLab>=16.8.0<=16.8.3
GitLab GitLab=16.9.0
GitLab GitLab>=16.8<16.8.3, >=16.9<16.9.1
16.8.316.9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.8.3Fixed in 16.9.1
  2. Upgrade

    Upgrade GitLab to a version that resolves this vulnerability.

    Fixed in 16.7.6
  3. Upgrade

    Upgrade GitLab to a version that resolves this vulnerability.

    Fixed in 16.8.3
  4. Upgrade

    Upgrade GitLab to a version that resolves this vulnerability.

    Fixed in 16.9.1
  5. Compensating control

    If you cannot upgrade immediately, restrict group sub-maintainer access so group members with the sub-maintainer role cannot change the title of shared private deploy keys (mitigates the incorrect authorization described for CVE-2023-3509).

Event History

Feb 21, 2024
CVE Published
via MITRE·10:57 PM
Data Sourced
via MITRE·10:57 PM
RemedyDescriptionSeverityWeakness
Apr 22, 2026
Data Sourced
via GitLab·08:52 AM
DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What versions are affected by CVE-2023-3509?

CVE-2023-3509 affects GitLab versions before 16.7.6, 16.8.0 to 16.8.2, and specifically 16.9.0.

2

What is the impact of CVE-2023-3509?

CVE-2023-3509 allows group members with sub-maintainer roles to change the title of privately accessible deploy keys.

3

How do I fix CVE-2023-3509?

To mitigate CVE-2023-3509, upgrade your GitLab instance to version 16.7.6 or apply the fixes in versions 16.8.3 and 16.9.1 or later.

4

Is CVE-2023-3509 a critical vulnerability?

CVE-2023-3509 is considered a moderate risk as it could lead to unauthorized changes to sensitive deploy keys.

5

Who can exploit CVE-2023-3509?

CVE-2023-3509 can be exploited by group members who have been assigned the sub-maintainer role.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203