dbcve.org
Sonar GerritApplication · Jenkins

CVE-2022-46688

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to after 377.v8f3808963dc5 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A cross-site request forgery (CSRF) vulnerability in Jenkins Sonar Gerrit Plugin 377.v8f3808963dc5 and earlier allows attackers to have Jenkins connect to Gerrit servers (previously configured by Jenkins administrators) using attacker-specified credentials IDs obtained through another method, potentially capturing credentials stored in Jenkins.

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

This is a CSRF vulnerability in Jenkins Sonar Gerrit Plugin versions 377.v8f3808963dc5 and earlier. The flaw allows authenticated attackers to trick Jenkins into connecting to previously configured Gerrit servers using attacker-specified credential IDs obtained through a separate vulnerability or attack vector, potentially enabling credential exfiltration.

MitigationUpgrade Jenkins Sonar Gerrit Plugin to version 378.v6d12_34a_e0dce1 or later to address the CSRF protection bypass. Additionally, ensure proper credential isolation and restrict administrative access to minimize the attack surface.

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
Sonar GerritApplication
Affected:<= 377.v8f3808963dc5

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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. Identify if Sonar Gerrit plugin is installed
    List installed Jenkins plugins via the web UI at /pluginManager/installed or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins
    Affected if The Sonar Gerrit plugin appears in the installed plugins list
  2. Check the installed version of Sonar Gerrit plugin
    In Jenkins web UI, go to /pluginManager/installed and locate Sonar Gerrit Plugin to view its version number
    Affected if The installed version is 377.v8f3808963dc5 or earlier
  3. Verify configured Gerrit server connections
    Navigate to Jenkins configured Sonar Gerrit plugin settings (typically under Manage Jenkins > System > Sonar Gerrit) and review any configured Gerrit servers
    Affected if One or more Gerrit servers are configured with stored credentials
  4. Review stored credentials accessible to the plugin
    Go to Manage Jenkins > Credentials and examine any credentials that the Sonar Gerrit plugin is configured to use, noting their IDs and types
    Affected if Credentials with arbitrary IDs are stored and the plugin has permission to access them
  5. Check for unexpected or unauthorized credential configurations
    Audit credential usage logs and compare configured credential IDs against known legitimate configurations
    Affected if Credential IDs in use differ from those originally configured or unauthorized credential usage is detected

You are affected if the Sonar Gerrit plugin is installed at version 377.v8f3808963dc5 or earlier and has configured Gerrit server connections with stored credentials.

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.

From vendor data
Upgrade available Upgrade to a release after 377.v8f3808963dc5
Interim mitigation

Upgrade Jenkins Sonar Gerrit Plugin to version 378.v6d12_34a_e0dce1 or later to address the CSRF protection bypass. Additionally, ensure proper credential isolation and restrict administrative access to minimize the attack surface.

Fix this in Sonar Gerrit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-46688 — 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-46688 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