# CVE-2022-43426: AWS secrets displayed without masking by Jenkins S3 Explorer Plugin

> Attackers can observe and capture AWS secret access keys because the Jenkins S3 Explorer Plugin fails to mask the form field.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2022
- **Updated:** 8 May 2025
- **Also known as:** GHSA-mf4p-wjrm-cmjp

## What is CVE-2022-43426?

CVE-2022-43426 is a medium-severity vulnerability in Jenkins S3 Explorer Plugin, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jenkins S3 Explorer Plugin 1.0.8 and earlier does not mask the AWS_SECRET_ACCESS_KEY form field, increasing the potential for attackers to observe and capture it.

Weakness: CWE-256 (Plaintext Storage of a Password)

## Which versions are affected by CVE-2022-43426?

2 open source packages ship an affected version, including io.jenkins.plugins:s3explorer. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.jenkins.plugins:s3explorer` | Maven | All versions to 1.0.8 | None |
| `io.jenkins.plugins:s3explorer` | Maven | All versions to 1.0.8 | None |

Products: Jenkins S3 Explorer.

## How do I fix CVE-2022-43426?

No fix has been published for CVE-2022-43426 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-43426 being exploited?

There is no known exploitation of CVE-2022-43426 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43426 and fix it if it is affected.

What it is: CVE-2022-43426 is a medium-severity vulnerability in Jenkins S3 Explorer Plugin, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-43426 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jenkins.plugins:s3explorer (Maven): affected all versions up to 1.0.8; no fix listed
- io.jenkins.plugins:s3explorer (Maven): affected all versions up to 1.0.8; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-43426/ (Markdown: https://insights.sbomify.com/CVE-2022-43426/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-43426
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-43426
- OSV: https://osv.dev/vulnerability/CVE-2022-43426

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-43426/
Summaries are generated and may contain mistakes; the official description above is the record.