podman-plugins vulnerabilities

Direct Vulnerabilities

Known vulnerabilities in the podman-plugins package. This does not include vulnerabilities belonging to this package’s dependencies.

How to fix?

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

Fix for free
VulnerabilityVulnerable Version
  • M
Use of Uninitialized Variable

*
  • M
Improper Input Validation

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • H
Uncontrolled Recursion

*
  • M
Uncontrolled Recursion

*
  • M
Resource Exhaustion

*
  • M
Improper Input Validation

*
  • H
Allocation of Resources Without Limits or Throttling

<4:4.9.4-10.el9_4
  • H
Information Exposure Through Log Files

<4:4.9.4-10.el9_4
  • M
Improper Input Validation

*
  • M
Improper Validation of Integrity Check Value

*
  • H
Memory Leak

<4:4.9.4-5.el9_4
  • M
Link Following

<4:4.9.4-3.el9_4
  • M
Improper Handling of Highly Compressed Data (Data Amplification)

<4:4.9.4-4.el9_4
  • M
Resource Exhaustion

<4:4.9.4-4.el9_4
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

<4:4.9.4-3.el9_4
  • H
Improper Input Validation

<4:4.9.4-10.el9_4
  • M
Improper Input Validation

<4:4.9.4-4.el9_4
  • M
Truncation of Security-relevant Information

<2:4.6.1-8.el9_3
  • M
Information Exposure

<2:4.9.4-0.1.el9
  • M
Resource Exhaustion

<2:4.9.4-0.1.el9
  • M
CVE-2023-39321

<2:4.6.1-7.el9_3
  • M
Cross-site Scripting (XSS)

<2:4.6.1-7.el9_3
  • M
Allocation of Resources Without Limits or Throttling

<2:4.6.1-7.el9_3
  • M
Cross-site Scripting (XSS)

<2:4.6.1-7.el9_3
  • M
Cross-site Scripting (XSS)

<2:4.6.1-5.el9
  • M
Resource Exhaustion

<2:4.6.1-7.el9_3
  • M
HTTP Response Splitting

<2:4.6.1-5.el9
  • M
Improper Handling of Unicode Encoding

<2:4.6.1-5.el9
  • M
Improper Handling of Unicode Encoding

<2:4.6.1-5.el9
  • M
Improper Handling of Unicode Encoding

<2:4.6.1-5.el9
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

<2:4.6.1-5.el9
  • M
Resource Exhaustion

<2:4.6.1-5.el9
  • M
Arbitrary Code Injection

<2:4.6.1-5.el9
  • M
Resource Exhaustion

<2:4.6.1-5.el9
  • M
Resource Exhaustion

<2:4.6.1-5.el9
  • M
Resource Exhaustion

<2:4.6.1-5.el9
  • M
Resource Exhaustion

<2:4.6.1-5.el9
  • M
Placement of User into Incorrect Group

<2:4.6.1-5.el9
  • M
Time-of-check Time-of-use (TOCTOU)

*
  • M
Allocation of Resources Without Limits or Throttling

<2:4.4.1-3.el9
  • M
Link Following

*
  • L
Directory Traversal

*
  • M
Algorithmic Complexity

*
  • M
CVE-2022-41715

*
  • M
Allocation of Resources Without Limits or Throttling

*
  • M
HTTP Request Smuggling

*
  • M
Resource Exhaustion

*
  • L
Placement of User into Incorrect Group

<2:4.2.0-7.el9_1
  • L
Placement of User into Incorrect Group

<2:4.2.0-7.el9_1
  • L
Resource Exhaustion

*
  • M
Information Exposure

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
HTTP Request Smuggling

*
  • M
Improper Input Validation

*
  • M
Insufficient Entropy

<2:4.4.1-3.el9
  • M
Use of a Broken or Risky Cryptographic Algorithm

<2:4.2.0-3.el9
  • M
Information Exposure

<2:4.2.0-3.el9
  • L
Access of Resource Using Incompatible Type ('Type Confusion')

*
  • M
Improper Input Validation

<2:4.2.0-3.el9
  • M
Origin Validation Error

<2:4.2.0-3.el9
  • M
Improper Input Validation

<2:4.2.0-3.el9
  • M
Improper Locking

<2:4.2.0-3.el9
  • M
Improper Validation of Array Index

<2:4.2.0-3.el9
  • M
Improper Validation of Array Index

<2:4.2.0-3.el9