dbcve.org
Mq NotifierApplication · Jenkins

CVE-2024-28154

MEDIUM · 6.5 CVSS v3.1 Published 2024-03-06
Fix available
A fix is available. Upgrade to 1.4.1 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 MQ Notifier Plugin 1.4.0 and earlier logs potentially sensitive build parameters as part of debug information in build logs by default.

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 MQ Notifier Plugin versions 1.4.0 and earlier unconditionally logs potentially sensitive build parameters (such as passwords, tokens, or credentials) as debug information in build logs, allowing unauthorized users with log access to view plaintext sensitive configuration data.

MitigationUpdate the MQ Notifier Plugin to a patched version once available, or remove/disable the plugin until fixed. Audit existing build logs for exposed sensitive data and rotate any credentials that may have been disclosed.

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
Mq NotifierApplication
Affected:< 1.4.1

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 MQ Notifier Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'MQ Notifier' in the list of installed plugins. Check the 'Version' column.
    Affected if The installed version is 1.4.0 or earlier, or the version cannot be determined (plugin present but version not shown indicates outdated).
  2. Identify jobs using MQ Notifier
    Search job configurations for 'mq-notifier' or 'MqNotifier' references. This can be done via the Jenkins script console using: Jenkins.instance.allItems.findAll { job -> job.builders.any { it.class.name?.contains('MqNotifier') || it.class.name?.contains('mq') } }.collect { it.fullName }
    Affected if Any jobs are found that have MQ Notifier configured as a build step.
  3. Inspect recent build logs for sensitive data
    Navigate to a job that uses MQ Notifier, then go to a recent build > Console Output. Search for 'DEBUG' level log entries from the MQ Notifier plugin, typically containing keywords like 'parameter', 'password', 'token', or 'credential'.
    Affected if Plaintext sensitive values (passwords, tokens, API keys) appear in debug log lines, especially in entries that mention build parameters.
  4. Search historical logs via file system
    If log files are archived, examine them in JENKINS_HOME/jobs/<jobname>/builds/<buildnumber>/log. Use grep or similar to search for sensitive-looking patterns in files named 'log' within build directories.
    Affected if Historical build log files contain plaintext sensitive data from MQ Notifier debug output.

A defender is affected if the MQ Notifier Plugin version is 1.4.0 or earlier AND the plugin is configured on any Jenkins jobs, with build logs potentially exposing plaintext sensitive parameters.

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 1.4.1 or later
Fixed in 1.4.1
Interim mitigation

Update the MQ Notifier Plugin to a patched version once available, or remove/disable the plugin until fixed. Audit existing build logs for exposed sensitive data and rotate any credentials that may have been disclosed.

Recommended fix High confidence

MQ Notifier Plugin version 1.4.1

  1. Log in to Jenkins as an administrator
  2. Navigate to 'Manage Jenkins'
  3. Click on 'Manage Plugins'
  4. Select the 'Installed' tab
  5. Locate the 'MQ Notifier' plugin in the list
  6. If an update is available, click 'Update' to upgrade to version 1.4.1 or later
  7. Alternatively, if the plugin is not currently installed, go to the 'Available' tab, search for 'MQ Notifier', and install version 1.4.1 or later
  8. After upgrade, restart Jenkins if required to apply the changes

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

Fix this in Mq Notifier 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-2024-28154 — 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-2024-28154 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