dbcve.org
Github Pull Request Coverage StatusApplication · Jenkins

CVE-2023-24442

MEDIUM · 5.5 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to after 2.2.0 or later.
See remediation →
57/100
Remediation priority · Elevated
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 GitHub Pull Request Coverage Status Plugin 2.2.0 and earlier stores the GitHub Personal Access Token, Sonar access token and Sonar password unencrypted in its global configuration file on the Jenkins controller where they can be viewed by users with access to the Jenkins controller file system.

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 GitHub Pull Request Coverage Status Plugin version 2.2.0 and earlier stores the GitHub Personal Access Token, Sonar access token, and Sonar password in plaintext (unencrypted) in its global configuration file on the Jenkins controller filesystem, allowing any user with file system access to view these sensitive credentials directly.

MitigationUpgrade to a patched version of the plugin that encrypts stored credentials. If no patched version is available, regenerate all exposed credentials (GitHub PAT, Sonar tokens/passwords) immediately and consider removing the plugin until a fix is available.

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
Github Pull Request Coverage StatusApplication
Affected:<= 2.2.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/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. Confirm the plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and look for 'GitHub Pull Request Coverage Status' in the list of installed plugins.
    Affected if The plugin named 'GitHub Pull Request Coverage Status' appears in the installed plugins list.
  2. Check the plugin version
    In the installed plugins list, note the version number displayed next to 'GitHub Pull Request Coverage Status'. Compare this version against the affected range: any version 2.2.0 or earlier.
    Affected if The installed version is 2.2.0 or any version lower (for example, 2.2.0, 2.1.0, 2.0.0, etc.).
  3. Locate the plugin configuration file
    On the Jenkins controller filesystem, locate the global configuration file for this plugin. This is typically found in the Jenkins home directory under the 'credentials' or 'secrets' folder, or within a plugin-specific XML configuration file that stores the plugin's settings.
    Affected if A configuration file related to 'GitHub Pull Request Coverage Status' or 'github-pullrequestcoverage' exists on the filesystem.
  4. Inspect for plaintext credentials
    Open the plugin's configuration file using a text editor or file viewer. Search for any of the following strings: GitHub Personal Access Token, Sonar access token, Sonar password, or similar credential fields. Look for unencrypted, readable token or password values (not wrapped in encryption markers).
    Affected if The file contains any of the credentials (GitHub PAT, Sonar token, or Sonar password) displayed as plaintext readable strings rather than encrypted values.

A user is affected if the GitHub Pull Request Coverage Status plugin version 2.2.0 or earlier is installed AND its configuration file contains plaintext (unencrypted) GitHub Personal Access Token, Sonar access token, or Sonar password values.

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 2.2.0
Interim mitigation

Upgrade to a patched version of the plugin that encrypts stored credentials. If no patched version is available, regenerate all exposed credentials (GitHub PAT, Sonar tokens/passwords) immediately and consider removing the plugin until a fix is available.

Recommended fix Moderate confidence

2.2.1 or later

  1. 1. Back up your Jenkins configuration (go to Manage Jenkins > Backup > Setup or use CLI jenkins-cli.jar for manual backup)
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Installed' tab and find 'GitHub Pull Request Coverage Status' plugin
  4. 4. If an update is available, check the plugin and click 'Download now and install after restart' or 'Update'
  5. 5. Wait for the plugin to download and install
  6. 6. Restart Jenkins (or wait for pending installations to complete if you selected 'install after restart')
  7. 7. After restart, go to Manage Jenkins > Configure System > GitHub Pull Request Coverage Status
  8. 8. Re-enter and save your GitHub Personal Access Token, Sonar access token, and Sonar password - these should now be stored encrypted
Caveat none expected - this is a security patch that adds encryption for stored credentials

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

Fix this in Github Pull Request Coverage Status Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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