Skip to content

Conversation

@arielkru
Copy link
Owner

@arielkru arielkru commented Feb 6, 2024

No description provided.

Copy link

@bridgecrew-dev bridgecrew-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bridgecrew has found errors in this PR ⬇️

import bleach
app = Flask(__name__)

app = Flask(__name__) # comment
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

HIGH  CSRF protections disabled
    File: flask.py | Checkov ID: CKV3_SAST_56

Description

CWE: CWE-352: Cross-Site Request Forgery (CSRF)
OWASP: A01:2021 - Broken Access Control

Cross-Site Request Forgery (CSRF) is an attack that forces a victim to execute unwanted actions on a web application they are authenticated with. By disabling CSRF protections, applications expose themselves to a serious security risk. This policy has identified instances where CSRF protections are disabled or not correctly implemented.

When CSRF protections are disabled, it can lead to:

  1. Unauthorized actions performed on behalf of an authenticated user.
  2. Data breaches.
  3. Account hijacking.
  4. Exploitation of the trust a user has with a specific site.

In the analyzed codebase, instances were detected where the CSRF protections were explicitly turned off. Such configurations increase the application's vulnerability to CSRF attacks.

For example, avoiding practices like:

# Disabling CSRF protection in Flask-WTF
class MyForm(flask_wtf.FlaskForm):
    class Meta:
        csrf = False

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants