CVE-2022-3331Public exploitNetwork attack vector

Cross-product issue disclosure via unchecked issue key

Published Oct 17, 2022 · Updated May 14, 2025

Authorization bypass in affected GitLab EE releases allows remote authenticated users to read unrelated ZenTao project issues. The issue-detail route accepts an attacker-controlled ZenTao issue key and fetches it without verifying that the issue belongs to the product ID configured for the GitLab project. Access to a GitLab project with the premium ZenTao integration is normally required, although a public project exposes the route without authentication; successful enumeration discloses issues from other ZenTao products available to the configured API key.

CVSS severity3.5
Low
EPSS probability0.61%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authorization bypass in affected GitLab EE releases allows remote authenticated users to read unrelated ZenTao project issues. The issue-detail route accepts an attacker-controlled ZenTao issue key and fetches it without verifying that the issue belongs to the product ID configured for the GitLab project. Access to a GitLab project with the premium ZenTao integration is normally required, although a public project exposes the route without authentication; successful enumeration discloses issues from other ZenTao products available to the configured API key.

The record

CVE
CVE-2022-3331
Published
Oct 17, 2022
Updated
May 14, 2025
Vendor
GitLab
Product
GitLab
Classifications
CWE-639, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 17, 2022CVE publishedPublication date reported by the CVE source.
  2. May 14, 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.

  1. Affected versionversion=>=14.5, <15.1.6
  2. Affected versionversion=>=15.2, <15.2.4
  3. Affected versionversion=>=15.3, <15.3.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=14.5, <15.1.6; version=>=15.2, <15.2.4; version=>=15.3, <15.3.2

Published CVSS scores

4.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
3.5GitLab Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-639Authorization Bypass Through User-Controlled Key
T1190Exploit Public-Facing Application

Public exploit references

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