4.3

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2025-53667

CVE-2025-53667: Jenkins Dead Man's Snitch Plugin vulnerability does not mask tokens

Jenkins Dead Man's Snitch Plugin 0.1 does not mask Dead Man's Snitch tokens displayed on the job configuration form, increasing the potential for attackers to observe and capture them.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2025-53667

CVE-2025-53667:

4.3

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
org.jenkins-ci.plugins:deadmanssnitch	maven	<= 0.1

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the insecure handling of the Dead Man's Snitch API token within the plugin. The core issue is that the token is treated as a standard 'String' throughout the 'DeadMansSnitchNotifier' class, rather than a secure credential.

The investigation of the plugin's source code revealed the following:

Data Binding: The DeadMansSnitchNotifier constructor is annotated with @DataBoundConstructor, indicating that Jenkins uses it to instantiate the class with values from the configuration form. The constructor public DeadMansSnitchNotifier(String token, String message) accepts the token as a plain String.
Configuration Form (UI): The corresponding UI is defined in src/main/resources/org/jenkinsci/plugins/deadmanssnitch/DeadMansSnitchNotifier/config.jelly. The form input for the token is defined as <f:textbox />. This Jelly tag renders a standard HTML text input field, which does not mask the characters entered by the user. The fix for this type of vulnerability is typically to use <f:password />, which would render a password field and integrate with Jenkins' credential encryption.
Insecure Storage: Because the token field is a String, Jenkins serializes it as plain text in the job's config.xml file on the controller's file system. This allows anyone with file system access or Item/ExtendedRead permissions to view the token.

The combination of the plain String field in the Java class and the <f:textbox /> in the Jelly view results in the token being neither masked in the UI nor encrypted at rest, leading to the reported vulnerability.

Vulnerable functions

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.