Stage View Plugin up to 2.26 on Jenkins inappropriate encoding for output context
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Stage View Plugin up to 2.26 on Jenkins. It has been rated as problematic. This issue affects some unknown processing. This manipulation causes inappropriate encoding for output context. This vulnerability is tracked as CVE-2022-43408. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic was found in Stage View Plugin up to 2.26 on Jenkins (Jenkins Plugin). Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a inappropriate encoding for output context vulnerability. The CWE definition for the vulnerability is CWE-838. The product uses or specifies an encoding when generating output to a downstream component, but the specified encoding is not the same as the encoding that is expected by the downstream component. As an impact it is known to affect integrity. The summary by CVE is:
Jenkins Pipeline: Stage View Plugin 2.26 and earlier does not correctly encode the ID of 'input' steps when using it to generate URLs to proceed or abort Pipeline builds, allowing attackers able to configure Pipelines to specify 'input' step IDs resulting in URLs that would bypass the CSRF protection of any target URL in Jenkins.
The weakness was disclosed 10/20/2022. The advisory is shared at openwall.com. This vulnerability is known as CVE-2022-43408 since 10/18/2022. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/09/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Inappropriate encoding for output contextCWE: CWE-838
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/18/2022 🔍10/20/2022 🔍
10/20/2022 🔍
05/09/2025 🔍
Sources
Advisory: openwall.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2022-43408 (🔍)
GCVE (CVE): GCVE-0-2022-43408
GCVE (VulDB): GCVE-100-211897
Entry
Created: 10/20/2022 16:01Updated: 05/09/2025 02:10
Changes: 10/20/2022 16:01 (39), 11/18/2022 16:11 (11), 05/09/2025 02:10 (17)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.