Client secret exposure via plaintext configuration response
Published Feb 12, 2020 · Updated Aug 4, 2024
Credential exposure in Jenkins Microsoft Entra ID Plugin 1.1.2 and earlier allows attackers to read a client secret from its configuration form. The global configuration form places the stored client secret into the browser response as plaintext instead of an encrypted value. Exposure requires an administrator to load the form and a browser extension, cross-site scripting flaw, or similar page-reading capability to capture the secret.
Summary
What happened
Credential exposure in Jenkins Microsoft Entra ID Plugin 1.1.2 and earlier allows attackers to read a client secret from its configuration form. The global configuration form places the stored client secret into the browser response as plaintext instead of an encrypted value. Exposure requires an administrator to load the form and a browser extension, cross-site scripting flaw, or similar page-reading capability to capture the secret.
The record
- CVE
- CVE-2020-2119
- Published
- Feb 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Jenkins Project
- Product
- Microsoft Entra ID (previously Azure AD) Plugin
- Classifications
- CWE-256, CWE-522, T1555.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 12, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.1.2
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