Use of a Broken or Risky Cryptographic Algorithm Affecting request-tracker4 package, versions <4.4.4+dfsg-2+deb11u4


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.02% (3rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use of a Broken or Risky Cryptographic Algorithm vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-DEBIAN11-REQUESTTRACKER4-9904174
  • published30 Apr 2025
  • disclosed5 May 2025

Introduced: 30 Apr 2025

CVE-2025-2545  (opens in a new tab)
CWE-327  (opens in a new tab)

How to fix?

Upgrade Debian:11 request-tracker4 to version 4.4.4+dfsg-2+deb11u4 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream request-tracker4 package and not the request-tracker4 package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

Vulnerability in Best Practical Solutions, LLC's Request Tracker prior to v5.0.8, where the Triple DES (3DES) cryptographic algorithm is used to protect emails sent with S/MIME encryption. Triple DES is considered obsolete and insecure due to its susceptibility to birthday attacks, which could compromise the confidentiality of encrypted messages.