CVE-2025-53666
BaseFortify
Publication date: 2025-07-09
Last updated on: 2025-11-04
Assigner: Jenkins Project
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jenkins | dead_man\s_snitch | 0.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-311 | The product does not encrypt sensitive or critical information before storage or transmission. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in Jenkins Dead Man's Snitch Plugin 0.1 involves storing Dead Man's Snitch tokens unencrypted in job config.xml files on the Jenkins controller. These tokens can be viewed by users who have Item/Extended Read permission or by anyone with access to the Jenkins controller file system.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized disclosure of sensitive tokens, which may allow attackers or unauthorized users to misuse these tokens, potentially compromising the security of Jenkins jobs or related systems.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by inspecting the Jenkins controller's job config.xml files for unencrypted Dead Man's Snitch tokens. You can search for these tokens by looking for specific token patterns or keywords related to Dead Man's Snitch within the config.xml files. For example, on the Jenkins controller file system, you might use commands like: grep -r 'deadmansnitch' /path/to/jenkins/jobs/*/config.xml or grep -r 'token' /path/to/jenkins/jobs/*/config.xml to find unencrypted tokens.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the Jenkins controller file system and limiting Item/Extended Read permissions to trusted users only. Additionally, avoid storing Dead Man's Snitch tokens unencrypted in job config.xml files. Consider removing or rotating exposed tokens and updating the plugin or Jenkins configuration to prevent storing sensitive tokens in plaintext.