Skip to content
New issue

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

Trivy Scan reports CVE-2021-33026 vulnerability in Flask-Caching v1.10.1 #323

Closed
nabz09 opened this issue Mar 11, 2022 · 1 comment
Closed

Comments

@nabz09
Copy link

nabz09 commented Mar 11, 2022

When running a Trivy scan on a Docker image which uses the Flask Caching dependency downloaded by pip, a critical vulnerability is thrown by the scan: https://nvd.nist.gov/vuln/detail/CVE-2021-33026
This is due to the use of the Pickle dependency.

Steps to reproduce:

  • Install Trivy following these steps: https://aquasecurity.github.io/trivy/v0.18.3/installation/

  • Create a new Docker image with flask caching, contents of Dockerfile
    FROM python:3.10
    RUN pip install flask-caching

  • Build the docker image:
    docker build -t flask-caching-image .

  • Run the Trivy security scan:
    trivy flask-caching-image

The output will list CVE-2021-33026 as a vulnerability of flask-caching

Expected Behaviour:

The scan should not pick up any CVEs for this project

Environment:

  • Python version: 3.10
  • Flask-Caching version: 1.10.1
@northernSage
Copy link
Member

Thanks for the heads up. This is a well known hassle of using pickle protocol as warned in python official docs and it has been extensively discussed in #209, so I won't get into it again. Since means of avoiding pickle have being added in pallets-eco/cachelib#63, considering the incoming integration with cachelib, I'll be closing this for now. Once again, thanks for letting us know.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

2 participants