Date ParameterApplication · Jenkins
CVE-2022-34185
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 · uneditedJenkins Date Parameter Plugin 0.0.4 and earlier does not escape the name and description of Date parameters on views displaying parameters, 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 confidenceThe Jenkins Date Parameter Plugin fails to escape user-supplied name and description fields for Date parameters when rendering parameter views, allowing injection of malicious scripts that execute when other users view the affected pages. This stored XSS requires Item/Configure permission to exploit, meaning an authenticated attacker with job configuration rights can inject the payload.
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
Date ParameterApplication
<= 0.0.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Date Parameter Plugin installationNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the CLI: `jenkins-cli.jar groovy --script 'println Jenkins.instance.pluginManager.plugins.find { it.shortName == "date-parameter" }?.version'Affected if Plugin is installed and version is 0.0.4 or lower (the vulnerable version range)
-
Locate jobs using Date ParameterSearch job configurations for '<dateParameter>' XML elements, or use Jenkins CLI: `jenkins-cli.jar list-jobs | xargs -I {} jenkins-cli.jar get-job {} | grep -i dateparameter`Affected if Any job is configured to use Date Parameter plugin (the vulnerable code path is triggered when Date Parameters exist)
-
Inspect Date parameter name and description fieldsFor each job with Date Parameters, view the job configuration under Parameters section. Examine the 'Name' and 'Description' fields of Date Parameter entries for unsanitized HTML or JavaScript syntax such as <script>, javascript:, onload, onerror, or other HTML tag injectionsAffected if Any Date Parameter has a name or description containing raw HTML tags, script elements, or event handler attributes (indicates exploitation in progress)
-
Review user permissions on configured jobsCheck who has Item/Configure permission on jobs with Date Parameters: Navigate to job > Configure > Apply, or review matrix authorization settings in Manage Jenkins > Configure Global SecurityAffected if Untrusted or unknown authenticated users have Item/Configure permission on jobs using Date Parameters (allows the authenticated attack vector)
A user is affected if they have the Date Parameter Plugin version 0.0.4 or lower installed AND have jobs configured with Date Parameters accessible to users with configuration rights.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to Date Parameter Plugin version 0.0.5 or later which properly escapes parameter names and descriptions. If upgrading is not immediately possible, restrict Item/Configure permission to trusted users only and monitor for suspicious parameter configurations.
Fix this in Date Parameter
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34185 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-34185 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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