AWS credential disclosure via unmasked configuration field
Published Oct 19, 2022 · Updated May 8, 2025
Information disclosure in Jenkins S3 Explorer Plugin 1.0.8 and earlier allows attackers to capture an AWS secret access key. The global configuration form renders AWS_SECRET_ACCESS_KEY as visible text instead of masking it, although s3explorer.xml encrypts the stored value. Exposure requires visibility of the populated form, after which the captured credential provides the access granted by its AWS permissions.
Summary
What happened
Information disclosure in Jenkins S3 Explorer Plugin 1.0.8 and earlier allows attackers to capture an AWS secret access key. The global configuration form renders AWS_SECRET_ACCESS_KEY as visible text instead of masking it, although s3explorer.xml encrypts the stored value. Exposure requires visibility of the populated form, after which the captured credential provides the access granted by its AWS permissions.
The record
- CVE
- CVE-2022-43426
- Published
- Oct 19, 2022
- Updated
- May 8, 2025
- Vendor
- Jenkins Project
- Product
- S3 Explorer
- Classifications
- CWE-256
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 19, 2022CVE publishedPublication date reported by the CVE source.
- May 8, 2025Record 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.0.8
What conditions does exploitation require?
What is affected?
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