We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could an attacker inject malicious code in place of the UID or consent payload?
Injecting a malicious UID in the cookie or URL parameter should be protected against by SQLAlchemy.
Currently, the consent payload is probably safe due to FastAPI and Pydantic. But if we need to make the schema more flexible, we need to be careful.
The text was updated successfully, but these errors were encountered:
andyhd
No branches or pull requests
Could an attacker inject malicious code in place of the UID or consent payload?
Injecting a malicious UID in the cookie or URL parameter should be protected against by SQLAlchemy.
Currently, the consent payload is probably safe due to FastAPI and Pydantic. But if we need to make the schema more flexible, we need to be careful.
The text was updated successfully, but these errors were encountered: