🛡️ CVE-2020-2297 — sms
Description
Access token stored in plain text by Jenkins SMS Notification Plugin
Jenkins SMS Notification Plugin 1.2 and earlier stores an access token unencrypted in its global configuration file com.hoiio.jenkins.plugin.SMSNotification.xml on the Jenkins controller as part of its configuration.
This access token can be viewed by users with access to the Jenkins controller file system.
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability none.
Weakness class
CVE-2020-2297 is classified as CWE-522: Insufficiently Protected Credentials. Credentials are stored or transmitted with protection too weak for what they unlock.
Affected software
CVE-2020-2297 is recorded against 1 package.
- com.hoiio.jenkins:sms
Timeline and source
Published on 24 May 2022 and last revised on 16 February 2024. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
nvd.nist.gov (Advisory)
github.com (Package)
www.jenkins.io (Web)
www.openwall.com (Web)
Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| com.hoiio.jenkins:sms | — | — |
References
More CVE 2020 advisories
Browse all of CVE 2020 in the advisory index.
Free Vulnerability Check
Is your site affected by CVE-2020-2297?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2020-2297 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.