dbcve.org
Validating Email ParameterApplication · Jenkins

CVE-2022-34791

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-30
Fix available
A fix is available. Upgrade to after 1.10 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 Validating Email Parameter Plugin 1.10 and earlier does not escape the name and description of its parameter type, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.

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 Validating Email Parameter Plugin versions 1.10 and earlier fails to properly escape output for the name and description fields of its parameter type. This allows stored XSS attacks where malicious JavaScript can be injected through these fields and executed when other users view the parameter configuration.

MitigationUpgrade the Validating Email Parameter Plugin to version 1.11 or later which includes proper output escaping. Alternatively, restrict Item/Configure permission to trusted users only.

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
Validating Email ParameterApplication
Affected:<= 1.10

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Check if Validating Email Parameter Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Validating Email Parameter' or list installed plugins via Jenkins CLI: jenkins-cli.jar or API call to /pluginManager/plugin/{validating-email-parameter}
    Affected if Plugin is not listed in installed plugins, then not affected. If listed, proceed to version check.
  2. Determine the installed version of the plugin
    In the Installed plugins tab, locate 'Validating Email Parameter' and note the Version column. Alternatively, examine the plugin's manifest file at $JENKINS_HOME/plugins/validating-email-parameter/META-INF/MANIFEST.MF for the Implementation-Version attribute.
    Affected if Version is 1.10 or earlier (e.g., 1.10, 1.9, 1.8, etc.)
  3. Verify if parameter configurations are accessible to untrusted users
    Review job configurations and parameter definitions. Check if jobs contain 'Validating Email Parameter' type parameters. Examine whether users with Item/Configure permission include untrusted or anonymous users.
    Affected if The plugin is installed at vulnerable version AND jobs contain Validating Email Parameter configurations accessible to users who are not fully trusted.
  4. Inspect the plugin's source for unescaped output (optional deeper check)
    If you have access to the Jenkins controller filesystem, examine the plugin jar at $JENKINS_HOME/plugins/validating-email-parameter/WEB-INF/classes for Jelly or Groovy view files that render the parameter name and description fields. Look for instances where these fields are rendered without using escBean, escape, or similar escaping functions.
    Affected if The view files render the name or description fields without proper HTML/JavaScript escaping.

Your environment is affected if the Validating Email Parameter Plugin version 1.10 or earlier is installed AND jobs using this parameter type are accessible to users who are not trusted with full Item/Configure permissions.

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.10
Interim mitigation

Upgrade the Validating Email Parameter Plugin to version 1.11 or later which includes proper output escaping. Alternatively, restrict Item/Configure permission to trusted users only.

Recommended fix Moderate confidence

Validating Email Parameter Plugin 1.11 or later

  1. Navigate to Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate 'Validating Email Parameter' plugin
  5. If version 1.10 or earlier is installed, click 'Update' to upgrade to the latest version

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

Fix this in Validating Email Parameter 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-2022-34791 — 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-34791 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