CVE-2024-34147 json
Jenkins Telegram Bot Plugin stores the Telegram Bot token in plaintext
published 2y ago modified 4mo ago also GHSA-94pr-w968-h923 , EUVD-2024-1539
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
Jenkins Telegram Bot Plugin 1.4.0 and earlier stores the Telegram Bot token unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.
Is CVE-2024-34147 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:telegrambot | <=1.4.0 |
no fix listed |
Affected products
- Jenkins Project Jenkins Telegram Bot Plugin
- jenkins jenkins-telegram-bot
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
jenkins.io
/security/advisory/2024-05-02/#SECURITY-3294
vendor-advisory, web
-
openwall.com
/lists/oss-security/2024/05/02/3
web, mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2024-34147
advisory
-
github.com
/jenkinsci/telegram-notifications-plugin
package
Sources
- CVE List CVE-2024-34147
- GitHub Advisory GHSA-94pr-w968-h923
- NVD CVE-2024-34147
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.