dbcve.org
JiraApplication · Jenkins

CVE-2023-49653

MEDIUM · 6.5 CVSS v3.1 Published 2023-11-29
Fix available
A fix is available. Upgrade to after 3.11 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 Jira Plugin 3.11 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.

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 Jira Plugin 3.11 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 is an authorization bypass in the plugin's credential handling where the context scope for credential lookup is improperly configured.

MitigationUpgrade Jenkins Jira Plugin to version 3.12 or later which implements proper context setting for credentials lookup.

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
JiraApplication
Affected:<= 3.11

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. Identify Jira Plugin installation status
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Jira' in the filter. Confirm the Jira Plugin is listed and installed.
    Affected if The Jira Plugin appears in the installed plugins list.
  2. Determine installed Jira Plugin version
    In the Installed plugins tab, locate the Jira Plugin and read the Version column. Compare this version number to the affected range (3.11 and earlier).
    Affected if The installed version is 3.11 or lower.
  3. Verify credentials are configured in Jenkins
    Navigate to Manage Jenkins > Manage Credentials. Review whether any credentials (such as API tokens, usernames, or passwords) are stored in any domain (System, Global, or item-specific).
    Affected if Credentials exist in any Jenkins credential store.
  4. Check for Jira Plugin configuration in jobs
    Examine Jenkins jobs (particularly Freestyle or Pipeline projects) that use Jira-related build steps or post-build actions. Inspect the job configuration to see if credentials are referenced or configured for Jira integration.
    Affected if A job has Jira Plugin functionality configured and references credentials.
  5. Review user permissions on jobs
    Under Manage Jenkins > Manage Users or in the Matrix Authorization Strategy, identify users or groups granted Item/Configure permission on specific projects or overall. Check if any users have configure permission on jobs that use Jira credentials they should not access.
    Affected if Users with Item/Configure permission exist on jobs that utilize Jira Plugin credentials.

The environment is affected if the Jira Plugin version is 3.11 or earlier, credentials are stored in Jenkins, and users with Item/Configure permission can access jobs that utilize Jira credentials they are not entitled to 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 3.11
Interim mitigation

Upgrade Jenkins Jira Plugin to version 3.12 or later which implements proper context setting for credentials lookup.

Recommended fix Moderate confidence

Jira Plugin version 3.11.1 or later (verify latest available version on plugins.jenkins.io)

  1. Navigate to Jenkins Manage Jenkins > Manage Plugins
  2. Go to the 'Installed' tab and locate the Jira Plugin
  3. Check if an update is available for the Jira Plugin
  4. If update available, select the plugin and click 'Update'
  5. After update, restart Jenkins if required
  6. Alternatively, download the fixed version manually from the Jenkins plugin repository and upload via 'Advanced' tab

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

Fix this in Jira Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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