CVE-2020-17495: Django celery results Django-celery-results Stores Sensitive Information Vulnerability

HIGH
Advisory Identifier: GHSA-fvx8-v524-8579
CVSS 7.5
CWE-312
Published
Advisory Summary

CVE-2020-17495 is a HIGH (CVSS 7.5) django-celery-results stores sensitive information vulnerability (CWE-312: Cleartext Storage of Sensitive Information) affecting Django celery results libraries in the PyPI ecosystem. The issue involves django-celery-results stores sensitive information in cleartext. Remediation is available by upgrading affected packages to version 2.4.0.

CVE-2020-17495 at a Glance

CVE Identifier CVE-2020-17495
GHSA Identifier GHSA-fvx8-v524-8579
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-312: Cleartext Storage of Sensitive Information
Affected Product Django celery results
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2020-17495

To remediate this vulnerability, upgrade all affected Django celery results dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

django-celery-results fixed: 2.4.0
pip install django-celery-results>=2.4.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show django-celery-results

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2020-17495, inspect your installed packages using pip:

pip show django-celery-results

Analyze the terminal output to locate any version of Django celery results in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.4.0), your application is affected.

Note: The pip show django-celery-results command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-312: Cleartext Storage of Sensitive Information, where the product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. In Django celery results, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

django-celery-results prior to 2.4.0 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database. In version 2.4.0 this is no longer the default behaviour but can be re-enabled with the `result_extended` flag in which case care should be taken to ensure any sensitive variables are scrubbed - see [here](https://github.com/celery/django-celery-results/issues/154#issuecomment-734706270) for an example.

CVE-2020-17495 Affected Django celery results Versions

1 component(s)
Fixed Versions:
2.4.0
Product / Package Ecosystem Affected Versions Fixed Version
django-celery-results
PyPI
< 2.4.0
2.4.0

References

Frequently Asked Questions

What is CVE-2020-17495?
CVE-2020-17495 is a security vulnerability in Django celery results involving django-celery-results Stores Sensitive Information In Cleartext under CWE-312: Cleartext Storage of Sensitive Information.
Which Django celery results versions are affected?
Affected versions include releases prior to 2.4.0 across affected packages: django-celery-results.
What version fixes CVE-2020-17495?
Upgrading to 2.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is django-celery-results affected?
Yes, django-celery-results is affected in releases prior to 2.4.0. Upgrade your dependency to 2.4.0 or later.
What is the CVSS score of CVE-2020-17495?
CVE-2020-17495 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2020-17495?
CVE-2020-17495 is classified under CWE-312: Cleartext Storage of Sensitive Information (The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.).
How can I check PyPI dependencies for CVE-2020-17495?
Run the dependency tree command: 'pip show django-celery-results'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fvx8-v524-8579",
  "modified" : "2024-09-13T20:13:25Z",
  "published" : "2021-06-04T21:46:52Z",
  "aliases" : [ "CVE-2020-17495" ],
  "summary" : "django-celery-results Stores Sensitive Information In Cleartext",
  "details" : "django-celery-results prior to 2.4.0 stores task results in the database. Among the data it stores are the variables passed into the tasks. The variables may contain sensitive cleartext information that does not belong unencrypted in the database.\n\nIn version 2.4.0 this is no longer the default behaviour but can be re-enabled with the `result_extended` flag in which case care should be taken to ensure any sensitive variables are scrubbed - see [here](https://github.com/celery/django-celery-results/issues/154#issuecomment-734706270) for an example.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "django-celery-results"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-17495"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/celery/django-celery-results/issues/142"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/celery/django-celery-results/issues/154"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/celery/django-celery-results/pull/316"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/celery/django-celery-results/commit/ad508fe3433499e5fc94645412d911e174863f28"
  }, {
    "type" : "ADVISORY",
    "url" : "https://github.com/advisories/GHSA-fvx8-v524-8579"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/celery/django-celery-results"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/django-celery-results/PYSEC-2020-38.yaml"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-312" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-05-17T21:40:19Z",
    "nvd_published_at" : "2020-08-11T21:15:00Z"
  }
}