dbcve.org
EasyqaApplication · Jenkins

CVE-2022-34203

HIGH · 8.8 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 1.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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 EasyQA Plugin 1.0 and earlier allows attackers to connect to an attacker-specified HTTP server.

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 EasyQA Plugin versions 1.0 and earlier allows authenticated users to be tricked into initiating connections from the Jenkins server to an attacker-controlled HTTP server, potentially enabling data exfiltration or internal network reconnaissance.

MitigationUpdate EasyQA Plugin to a patched version if available; otherwise disable or remove the plugin until a fix is released. Additionally, ensure Jenkins is configured with CSRF protection 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
EasyqaApplication
Affected:<= 1.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Check if EasyQA plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar or check $JENKINS_HOME/plugins/ for easyqa folder
    Affected if EasyQA plugin is present in the list of installed plugins
  2. Identify EasyQA plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, locate EasyQA and note the version column; or check the version file in $JENKINS_HOME/plugins/easyqa/META-INF/MANIFEST.MF
    Affected if Version is 1.0 or earlier, or version cannot be determined (plugin too old)
  3. Verify authentication is required for the vulnerable action
    Review EasyQA plugin configuration at Manage Jenkins > Configure System > EasyQA settings. Confirm that any configured credentials or integrations require valid authentication
    Affected if No authentication is enforced on EasyQA plugin features, or anonymous users can trigger plugin actions
  4. Confirm CSRF protection is enabled in Jenkins
    Go to Manage Jenkins > Configure Global Security > CSRF Protection section. Verify that "Enable CSRF Protection" is checked, or check config.xml for <crumbDefaultSuffix> setting
    Affected if CSRF protection is disabled or not configured (this is a defense-in-depth measure that would mitigate the vulnerability)

You are affected if the EasyQA plugin is installed with version 1.0 or earlier and CSRF protection is disabled in Jenkins.

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

Update EasyQA Plugin to a patched version if available; otherwise disable or remove the plugin until a fix is released. Additionally, ensure Jenkins is configured with CSRF protection enabled as a defense-in-depth measure.

Recommended fix Moderate confidence

EasyQA Plugin version 1.1 or later

  1. Navigate to 'Manage Jenkins' > 'Manage Plugins' in the Jenkins dashboard
  2. Go to the 'Installed' tab to view currently installed plugins
  3. Locate the EasyQA Plugin in the list
  4. If a newer version is available, select it and click 'Update'
  5. After updating, restart Jenkins to apply the changes
  6. Alternatively, if no update is available via the UI, download the newer plugin (.hpi) from the Jenkins plugin repository and upload it via 'Advanced' > 'Upload Plugin'
Caveat Review release notes for any configuration changes required after upgrading

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

Fix this in Easyqa Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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