CVE-2022-2095: 
GitLab vulnerability analysis and mitigation

An improper access control check in GitLab CE/EE affecting all versions starting from 13.7 before 15.0.5, all versions starting from 15.1 before 15.1.4, and all versions starting from 15.2 before 15.2.1 allows a malicious authenticated user to view a public project's Deploy Key's public fingerprint and name when that key has write permission. Note that GitLab never asks for nor stores the private key (GitLab Security Release, NVD).

The vulnerability exists in the deploy keys autocomplete endpoint which only checks if the user can view the repository, not if they have write access to it. This differs from the REST API implementation which properly restricts access. The autocomplete endpoint at '/-/autocomplete/deploykeyswith_owners' allows unauthorized viewing of deploy keys by only checking repository view permissions (HackerOne Report).

The vulnerability allows non-project members to view deploy keys of public projects, potentially exposing sensitive project access information. While GitLab never stores private keys, exposure of public key fingerprints and names could provide attackers with information about project deployment infrastructure (GitLab Security Release).

Users should upgrade to GitLab versions 15.0.5, 15.1.4, or 15.2.1 or later which contain the fix for this vulnerability. The issue has been patched by properly implementing access controls in the deploy keys autocomplete endpoint (GitLab Security Release).