Stored XSS via unescaped webhook build cause
Published Jun 30, 2022 · Updated Aug 3, 2024
Stored XSS in Jenkins GitLab Plugin 1.5.34 and earlier allows remote authenticated users to execute script via webhook build causes. GitLabWebHookCause/description.jelly renders an HTML-formatted shortDescription containing user-controlled webhook fields without safely neutralizing them. Item/Configure permission and a viewer opening the affected build cause are required, exposing data and actions available in the viewer's Jenkins session.
Summary
What happened
Stored XSS in Jenkins GitLab Plugin 1.5.34 and earlier allows remote authenticated users to execute script via webhook build causes. GitLabWebHookCause/description.jelly renders an HTML-formatted shortDescription containing user-controlled webhook fields without safely neutralizing them. Item/Configure permission and a viewer opening the affected build cause are required, exposing data and actions available in the viewer's Jenkins session.
The record
- CVE
- CVE-2022-34777
- Published
- Jun 30, 2022
- Updated
- Aug 3, 2024
- Vendor
- Jenkins Project
- Product
- GitLab Plugin
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=1.5.34
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo