Scan Another

CVE Scan for linuxserver/speedtest-tracker:latest

Docker image vulnerability scanner

24 Known Vulnerabilities in this Docker Image

0
Critical
1
High
10
Medium
1
Low
0
Info/ Unspecified/ Unknown
CVE IDSeverityPackageAffected VersionFixed VersionCVSS Score
CVE-2025-67507highfilament>=4.0.0,<4.3.14.3.18.1

Summary

A flaw in the handling of recovery codes for app-based multi-factor authentication allows the same recovery code to be reused indefinitely. This issue does not affect email-based MFA. It also only applies when recovery codes are enabled.

Impact

If an attacker gains access to both the user's password and their recovery codes, they can repeatedly complete MFA without the user's app-based second factor. This weakens the expected security of MFA by turning recovery codes into a static, long-term bypass method.

Relevance:

The CVE might be relevant if the Docker image uses vulnerable dependencies or configurations that could be exploited in a multi-tenant environment where untrusted users have access. It could be critical if the vulnerability allows privilege escalation or unauthorized access to the host system. Always check if the specific components affected by the CVE are used in the image's deployment. (Note: Relevance analysis is automatically generated and may require verification.)

Package URL(s):
  • pkg:composer/filament/filament@4.1.0
CVE-2025-48964mediumiputils<=20240905-r0not fixed6.5
CVE-2025-60876mediumssl_client<=1.37.0-r20not fixed6.5
CVE-2025-47268mediumiputils<=20240905-r0not fixed6.5
CVE-2025-13034mediumlibcurl<=8.14.1-r2not fixed5.9
CVE-2026-22796mediumopenssl<3.5.5-r03.5.5-r05.3
CVE-2025-14524mediumlibcurl<=8.14.1-r2not fixed5.3
CVE-2025-15079mediumlibcurl<=8.14.1-r2not fixed5.3
CVE-2025-14819mediumlibcurl<=8.14.1-r2not fixed5.3
CVE-2016-2781mediumcoreutils<=9.7-r1not fixed4.6

Severity Levels

Exploitation could lead to severe consequences, such as system compromise or data loss. Requires immediate attention.

Vulnerability could be exploited relatively easily and lead to significant impact. Requires prompt attention.

Exploitation is possible but might require specific conditions. Impact is moderate. Should be addressed in a timely manner.

Exploitation is difficult or impact is minimal. Address when convenient or as part of regular maintenance.

Severity is not determined, informational, or negligible. Review based on context.

Sliplane Icon
About Sliplane

Sliplane is a simple container hosting solution. It enables you to deploy your containers in the cloud within minutes and scale up as you grow.

Try Sliplane for free

About the CVE Scanner

What is a CVE?

CVE stands for Common Vulnerabilities and Exposures. It is a standardized identifier for known security vulnerabilities, allowing developers and organizations to track and address potential risks effectively. For more information, visit cve.mitre.org.

About the CVE Scanner

The CVE Scanner is a powerful tool that helps you identify known vulnerabilities in your Docker images. By scanning your images against a comprehensive database of Common Vulnerabilities and Exposures (CVEs), you can ensure that your applications are secure and up-to-date. For more details, checkout the NIST CVE Database.

How the CVE Scanner Works

The CVE Scanner analyzes your Docker images against a comprehensive database of known vulnerabilities. It uses Docker Scout under the hood to provide detailed insights into affected packages, severity levels, and available fixes, empowering you to take immediate action.

Why CVE Scanning is Essential for Your Docker Images

With the rise of supply chain attacks, ensuring the security of your applications has become more critical than ever. CVE scanning plays a vital role in identifying vulnerabilities that could be exploited by attackers, especially those introduced through dependencies and third-party components. Regularly scanning and securing your Docker images is essential to protect your applications from these evolving threats.

Benefits of CVE Scanning

  • Enhanced Security: Detect and mitigate vulnerabilities before they are exploited.
  • Compliance: Meet industry standards and regulatory requirements for secure software.
  • Proactive Maintenance: Stay ahead of potential threats by addressing vulnerabilities early.

The Importance of Patching Docker Images

Patching your Docker images is a critical step in maintaining the security and stability of your applications. By regularly updating your images to include the latest security patches, you can address known vulnerabilities and reduce the risk of exploitation. This proactive approach ensures that your applications remain resilient against emerging threats and helps maintain compliance with security best practices.

Want to deploy this image?

Try out Sliplane - a simple Docker hosting solution. It provides you with the tools to deploy, manage and scale your containerized applications.