dbcve.org
GitLabApplication

CVE-2022-3483

MEDIUM · 5.4 CVSS v3.1 Published 2022-11-09
Fix available
A fix is available. Upgrade to 15.3.5 / 15.4.4 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.1 before 15.3.5, all versions starting from 15.4 before 15.4.4, all versions starting from 15.5 before 15.5.2. A malicious maintainer could exfiltrate a Datadog integration's access token by modifying the integration URL such that authenticated requests are sent to an attacker controlled server.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A malicious GitLab maintainer can modify the Datadog integration URL to redirect authenticated API requests to an attacker-controlled server, enabling exfiltration of the Datadog access token through the integration's outbound HTTP requests.

MitigationUpgrade GitLab to version 15.3.5, 15.4.4, 15.5.2 or later to receive the patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 12.1.0, < 15.3.5>= 15.4.0, < 15.4.4>= 15.5.0, < 15.5.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check your GitLab version
    Run `gitlab-rake gitlab:env:info` or check the GitLab admin area at /admin/about to find the installed GitLab version.
    Affected if The installed version falls within any of these ranges: 12.1.0 to 15.3.4, 15.4.0 to 15.4.3, or 15.5.0 to 15.5.1.
  2. Verify if Datadog integration is configured
    Navigate to the GitLab admin area, go to Integrations (or settings), and check if the Datadog integration is enabled. Alternatively, check the gitlab.yml configuration file for datadog settings.
    Affected if The Datadog integration is enabled and has an API token configured.
  3. Inspect the Datadog integration URL setting
    In the GitLab admin integration settings for Datadog, examine the 'URL' field. Verify if it points to an expected Datadog endpoint (typically app.datadoghq.com) or an unrecognized third-party domain.
    Affected if The Datadog integration URL is set to a domain other than the official Datadog endpoints (e.g., app.datadoghq.com), indicating potential tampering.
  4. Review audit logs for Datadog integration changes
    Check GitLab audit logs (under Admin Area > Monitoring > Audit Events) for any changes to the Datadog integration configuration, focusing on modifications to the URL and API token fields.
    Affected if Audit logs show recent changes to the Datadog integration settings, especially URL modifications by an unexpected user.

You are affected if your GitLab version is in the vulnerable range AND the Datadog integration is enabled with a potentially compromised or misconfigured URL.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 15.3.5 / 15.4.4 / 15.5.2 or later
Fixed in 15.3.515.4.415.5.2
Interim mitigation

Upgrade GitLab to version 15.3.5, 15.4.4, 15.5.2 or later to receive the patch.

Recommended fix High confidence

15.5.2 (or latest stable release)

  1. 1. Identify the current GitLab version by navigating to the GitLab Admin area or running `sudo gitlab-rake gitlab:env:info`
  2. 2. Plan upgrade to one of the fixed versions: 15.3.5, 15.4.4, or 15.5.2 (recommended: 15.5.2 or latest stable)
  3. 3. Create a full backup of the GitLab instance using `sudo gitlab-backup-create`
  4. 4. Update the package repository and upgrade GitLab using the official upgrade method for your installation type (omnibus, source, etc.)
  5. 5. Reconfigure GitLab after upgrade using `sudo gitlab-ctl reconfigure`
  6. 6. Verify the upgrade was successful and GitLab is functioning properly
  7. 7. Review the Datadog integration settings to ensure configuration integrity
Caveat Point releases typically do not include breaking changes, but review release notes for your specific upgrade path

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3483 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3483 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data