CVE-2025-53666

Vulnerability

Description

The Jenkins Dead Man's Snitch Plugin 0.1 stores Dead Man's Snitch tokens unencrypted in job config.xml files on the Jenkins controller [1][3]. This means the tokens are persisted in plaintext without any masking or encryption, making them accessible to anyone who can read those configuration files.

Exploitation

Prerequisites

An attacker needs either the Item/Extended Read permission on a Jenkins job or direct access to the Jenkins controller's file system to view the stored tokens [1][3]. No additional authentication is required beyond those permissions. The attack surface is limited to users or processes that already have some level of access to the Jenkins instance.

Impact

If an attacker obtains the Dead Man's Snitch token, they can potentially interact with the Dead Man's Snitch service, which is used for monitoring and alerting. The exact impact depends on the token's privileges, but it could allow an attacker to disable or manipulate monitoring alerts, or gain further insight into the monitored infrastructure.

Mitigation

Status

As of the Jenkins Security Advisory 2025-07-09, no fix has been released for this plugin [1][2]. The plugin is listed among unresolved security issues, meaning users must either remove the plugin or restrict access to job configurations and the controller file system as a workaround [2].