CVE Scan for langgenius/dify-api:release-e-1.8.1
Docker image vulnerability scanner
63 Known Vulnerabilities in this Docker Image
| CVE ID | Severity | Package | Affected Version | Fixed Version | CVSS Score |
|---|---|---|---|---|---|
| CVE-2024-52338 | critical | pkg:pypi/[email protected] | >=4.0.0,<17.0.0 | 17.0.0 | 9.8 |
Deserialization of untrusted data in IPC and Parquet readers in the Apache Arrow R package versions 4.0.0 through 16.1.0 allows arbitrary code execution. An application is vulnerable if it reads Arrow IPC, Feather or Parquet data from untrusted sources (for example, user-supplied input files). This vulnerability only affects the arrow R package, not other Apache Arrow implementations or bindings unless those bindings are specifically used via the R package (for example, an R application that embeds a Python interpreter and uses PyArrow to read files from untrusted sources is still vulnerable if the arrow R package is an affected version). It is recommended that users of the arrow R package upgrade to 17.0.0 or later. Similarly, it is recommended that downstream libraries upgrade their dependency requirements to arrow 17.0.0 or later. If using an affected version of the package, untrusted data can read into a Table and its internal to_data_frame() method can be used as a workaround (e.g., read_parquet(..., as_data_frame = FALSE)$to_data_frame()). This issue affects the Apache Arrow R package: from 4.0.0 through 16.1.0. Users are recommended to upgrade to version 17.0.0, which fixes the issue. Relevance: The CVE-2024-52338 is relevant if the Docker image uses vulnerable versions of `setuptools` (<= 69.0.3), as it could allow arbitrary code execution during package installation. It would be critical if an attacker can manipulate the installation process, such as in a compromised build environment or malicious package source. For normal usage of the pre-built image, the risk is low unless custom builds or untrusted dependencies are introduced. (Note: Relevance analysis is automatically generated and may require verification.) Package URL(s):
More Info (NVD): | |||||
| CVE-2025-9230 | high | openssl | <3.0.17-1~deb12u3 | 3.0.17-1~deb12u3 | 7.5 |
| CVE-2025-59420 | high | pkg:pypi/[email protected] | <1.6.4 | 1.6.4 | 7.5 |
| CVE-2025-59375 | high | expat | >=2.5.0-1+deb12u2 | not fixed | 7.5 |
| CVE-2023-24807 | high | pkg:npm/[email protected] | <5.19.1 | 5.19.1 | 7.5 |
| CVE-2024-23342 | high | pkg:pypi/[email protected] | >=0 | not fixed | 7.4 |
| CVE-2025-50817 | high | pkg:pypi/[email protected] | >=0.14.0 | not fixed | 7.3 |
| CVE-2025-22150 | medium | pkg:npm/[email protected] | >=4.5.0,<5.28.5 | 5.28.5 | 6.8 |
| CVE-2025-47906 | medium | pkg:golang/[email protected] | >=1.24.0,<1.24.6 | 1.24.6 | 6.5 |
| CVE-2025-8869 | medium | pkg:pypi/[email protected] | <=25.2 | not fixed | 5.9 |
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 is a simple container hosting solution. It enables you to deploy your containers in the cloud within minutes and scale up as you grow.
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.
Sliplane is not associated with Docker Inc. or any of its products. Prices do not include VAT.