[Snyk] Fix for 3 vulnerabilities

[madchap]

Snyk has created this PR to fix 3 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

• requirements.txt

⚠️ Warning

celery 5.3.0 requires kombu, which is not installed.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.
• Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Type Confusion
🦉 Denial of Service (DoS)

[secureflag-knowledge-base]

Type Juggling

Play Labs on this vulnerability with SecureFlag!

Description

Type Juggling (also known as Type Confusion) vulnerabilities are a class of vulnerability wherein an object is initialized or accessed as the incorrect type, allowing an attacker to potentially bypass authentication or undermine the type safety of an application, possibly leading to arbitrary code execution.

Read more

Impact

A successful Type Juggling attack can result in the complete compromise of the confidentiality, integrity, and availability of the target system. For example, the type confusion vulnerability CVE-2015-0336 in Adobe Flash Player allows an attacker to execute arbitrary code, which could lead to unauthorized access or the modification of data.

Prevention

In development, it is essential to ensure that resources are initialized and accessed as the intended type.

In statically-typed languages, take extra care where type casting occurs, using the strictest cast or type possible (i.e., in the case of handling a subclass, cast to the subclass rather than the parent). In a dynamically-typed language, type casting can occur implicitly, for example, in PHP "0e1" == "0" evaluates to true, as 0e1 is cast to the integer 0. In these cases, it is important to use strict comparators such as === in PHP.

Testing

Verify that data is strongly typed and validated against a defined schema. Verify also that strict comparison is used wherever possible and that objects cannot be initialized with or accessed through the incorrect type.

• OWASP ASVS: 5.1.4
• OWASP Testing Guide: Test Defenses Against Application Misuse, Business Logic Testing

View this in the SecureFlag Knowledge Base