Bot token disclosure via plaintext configuration storage
Published May 2, 2024 · Updated Feb 13, 2025
Credential exposure in Jenkins Telegram Bot Plugin 1.4.0 and earlier allows local users to read the Telegram Bot token. The global configuration serializer writes the token unencrypted to jenkinsci.plugins.telegrambot.TelegramBotGlobalConfiguration.xml on the controller. Access requires permission to read the controller file system, and disclosure enables use of the configured bot identity.
Summary
What happened
Credential exposure in Jenkins Telegram Bot Plugin 1.4.0 and earlier allows local users to read the Telegram Bot token. The global configuration serializer writes the token unencrypted to jenkinsci.plugins.telegrambot.TelegramBotGlobalConfiguration.xml on the controller. Access requires permission to read the controller file system, and disclosure enables use of the configured bot identity.
The record
- CVE
- CVE-2024-34147
- Published
- May 2, 2024
- Updated
- Feb 13, 2025
- Vendor
- Jenkins Project
- Product
- Telegram Bot Plugin
- Classifications
- CWE-522, T1552.001
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 2, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=-
- Affected versionversion=0 <=1.4.0
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