dbcve.org
Jianliao NotificationApplication · Jenkins

CVE-2022-34205

MEDIUM · 6.5 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 1.1 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 Jianliao Notification Plugin 1.1 and earlier allows attackers to send HTTP POST requests to an attacker-specified URL.

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

CSRF vulnerability in Jenkins Jianliao Notification Plugin version 1.1 and earlier allows authenticated or unauthenticated attackers to trick authenticated users into sending HTTP POST requests to attacker-controlled URLs. The plugin lacks proper CSRF token validation on its notification endpoints, enabling malicious cross-site request forgery attacks that could result in data exfiltration or triggering unintended actions through the victim's session.

MitigationUpdate the Jenkins Jianliao Notification Plugin to the latest patched version. If no update is available, disable or remove the plugin until a patch is released. Additionally, ensure Jenkins global CSRF protection is enabled as a defense-in-depth measure.

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
Jianliao NotificationApplication
Affected:<= 1.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 if Jenkins Jianliao Notification Plugin is installed
    Run the following Groovy script in Jenkins Script Console (Manage Jenkins > Script Console): Jenkins.instance.pluginManager.plugins.each { if (it.shortName == 'jenkinsci/jianliao-notification-plugin') { println 'Plugin found: ' + it.displayName + ' Version: ' + it.version } }. Alternatively, check the plugin manifest file at $JENKINS_HOME/plugins/jianliao-notification/META-INF/MANIFEST.MF for the Plugin-Version attribute.
    Affected if The plugin is not found in the output or directory does not exist - NOT AFFECTED. If found, proceed to next check.
  2. Confirm installed plugin version is vulnerable
    Compare the version identified in step 1 against the affected range. Jianliao Notification Plugin version 1.1 and earlier are vulnerable. If running version 1.1 or lower, the plugin is vulnerable.
    Affected if The installed version is 1.1 or earlier - AFFECTED. If running version 1.2 or higher - NOT AFFECTED.
  3. Determine if notification endpoint is accessible
    Check if any Jenkins jobs have the Jianliao Notification post-build action configured. Inspect job configuration XML files in $JENKINS_HOME/jobs/<jobname>/config.xml for the presence of <com.tikal.jenkins.plugins.notification.JianliaoNotificationPublisher> element, or check job configurations via Jenkins UI at each job's Configure page under Post-build Actions.
    Affected if No jobs have the Jianliao notification post-build action configured - LOWER RISK (though CSRF vulnerability in the plugin still exists when enabled). If notification endpoints are configured and reachable, the CSRF vulnerability is exploitable.

The environment is affected if the Jenkins Jianliao Notification Plugin version 1.1 or earlier is installed and the notification feature is configured for any Jenkins job, as this enables the vulnerable CSRF-protected endpoints.

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

Update the Jenkins Jianliao Notification Plugin to the latest patched version. If no update is available, disable or remove the plugin until a patch is released. Additionally, ensure Jenkins global CSRF protection is enabled as a defense-in-depth measure.

Fix this in Jianliao Notification 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-2022-34205 — 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-34205 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