odo.src vulnerabilities

Direct Vulnerabilities

Known vulnerabilities in the odo.src package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free
VulnerabilityVulnerable Version
  • H
Cross-site Scripting (XSS)

*
  • H
Directory Traversal

*
  • H
Authorization Bypass Through User-Controlled Key

*
  • M
Allocation of Resources Without Limits or Throttling

*
  • L
Resource Exhaustion

*
  • M
Cross-site Scripting (XSS)

*
  • M
Improper Check for Unusual or Exceptional Conditions

*
  • M
Use of Uninitialized Variable

*
  • M
Improper Handling of Unicode Encoding

*
  • M
Improper Handling of Unicode Encoding

*
  • M
Resource Exhaustion

*
  • M
CVE-2022-41715

*
  • M
Resource Exhaustion

*
  • M
Incorrect Regular Expression

*
  • M
Directory Traversal

*
  • M
Resource Exhaustion

*
  • M
HTTP Request Smuggling

*
  • M
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

*
  • M
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

*
  • H
CVE-2023-28154

*
  • M
Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

*
  • H
Improper Input Validation

*
  • H
Improper Handling of Unicode Encoding

*
  • H
Resource Exhaustion

*
  • H
Improper Authorization

*
  • H
Improper Validation of Syntactic Correctness of Input

*
  • L
Improper Handling of Exceptional Conditions

*
  • M
HTTP Request Smuggling

*
  • L
Insufficient Entropy

*
  • L
Improper Verification of Cryptographic Signature

*
  • M
Improper Input Validation

*
  • M
Improper Input Validation

*
  • M
Placement of User into Incorrect Group

*
  • M
Resource Exhaustion

*
  • M
Buffer Overflow

*
  • M
Algorithmic Complexity

*
  • M
Integer Overflow or Wraparound

*
  • M
Cleartext Transmission of Sensitive Information

*
  • M
Out-of-bounds Read

*
  • M
Cross-site Scripting (XSS)

*
  • M
Use of a Broken or Risky Cryptographic Algorithm

*
  • M
Resource Exhaustion

*
  • M
Resource Exhaustion

*
  • M
Information Exposure

*
  • M
Information Exposure

*
  • M
Missing Release of Resource after Effective Lifetime

*
  • M
Truncation of Security-relevant Information

*
  • M
Resource Exhaustion

*
  • M
Loop with Unreachable Exit Condition ('Infinite Loop')

*
  • M
Arbitrary Code Injection

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
Resource Exhaustion

*
  • M
Information Exposure

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
Inefficient Regular Expression Complexity

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
Improperly Controlled Sequential Memory Allocation

*
  • M
Open Redirect

*
  • M
HTTP Request Smuggling

*
  • H
Allocation of Resources Without Limits or Throttling

*
  • H
Memory Leak

*
  • H
Resource Exhaustion

*
  • C
Directory Traversal

*
  • H
Arbitrary Argument Injection

*
  • H
Exposure of Private Information ('Privacy Violation')

*
  • H
Resource Exhaustion

*