dbcve.org
WarningsApplication · Jenkins

CVE-2023-46651

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to after 10.5.0 or later.
See remediation →
71/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
Jenkins Warnings Plugin 10.5.0 and earlier does not set the appropriate context for credentials lookup, allowing attackers with Item/Configure permission to access and capture credentials they are not entitled to. This fix has been backported to 10.4.1.

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

The Jenkins Warnings Plugin versions 10.5.0 and earlier has an improper access control vulnerability where it fails to set the appropriate context for credential lookup. This allows authenticated users with Item/Configure permission to access and capture credentials they are not entitled to, effectively enabling credential theft by privileged insiders.

MitigationUpdate the Jenkins Warnings Plugin to version 10.4.1 or later (the fix was backported to 10.4.1) or to the latest available version. Review user permissions and audit logs for any unauthorized credential access.

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
WarningsApplication
Affected:<= 10.5.0

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Verify Jenkins Warnings Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Warnings' in the list, or check the plugin directory $JENKINS_HOME/plugins/ for the warnings plugin folder.
    Affected if The plugin is present in the installed plugins list.
  2. Determine the installed version of Warnings Plugin
    In the Manage Plugins > Installed tab, locate the Warnings Plugin and note the Version column. Alternatively, check the plugin's manifest file at $JENKINS_HOME/plugins/warnings/META-INF/MANIFEST.MF for the Implementation-Version attribute.
    Affected if The installed version is 10.5.0 or earlier.
  3. Identify users with Item/Configure permission
    Navigate to Manage Jenkins > Manage Users and review user accounts. Check Job > Configure permissions in folder/project configurations. Users with Item/Configure permission on any job can potentially exploit this vulnerability.
    Affected if There are users granted Item/Configure permission on jobs or folders they should not fully control.
  4. Audit Jenkins logs for credential access patterns
    Review Jenkins logs (Main Jenkins > System Log > All Jenkins Logs) or the audit log for patterns of credential retrieval tied to users with limited permissions. Look for accesses to credentials from the Credentials Plugin by users who should not have access.
    Affected if Unusual credential lookup events by users with only Item/Configure permission are found.

A user is affected if they have Jenkins Warnings Plugin version 10.5.0 or earlier installed AND have users with Item/Configure permission on jobs or folders that contain credentials they should not access.

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 a release after 10.5.0
Interim mitigation

Update the Jenkins Warnings Plugin to version 10.4.1 or later (the fix was backported to 10.4.1) or to the latest available version. Review user permissions and audit logs for any unauthorized credential access.

Recommended fix High confidence

10.4.1 or later

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the Updates tab
  4. 4. Locate the Warnings Plugin in the list of available updates
  5. 5. Select the Warnings Plugin and click Download now and install after restart, or update to version 10.4.1 or later
  6. 6. Wait for the plugin to update and Jenkins to restart

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

Fix this in Warnings Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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