Improper Verification of Cryptographic Signature in django-rest-registration
CVE-2019-13177GHSA-p3w6-jcg4-52xh
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (django-rest-registration 0.5.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- >= 0.2.0, < 0.5.0
- Fixed in
- 0.5.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-p3w6-jcg4-52xh lists affected ranges: PyPI django-rest-registration >=0.2.0 <0.5.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-p3w6-jcg4-52xh lists affected ranges: PyPI django-rest-registration >=0.2.0 <0.5.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2019-13177: 1.64% estimated exploitation activity in the next 30 days; percentile 76.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Misusing the Django Signer API leads to predictable signatures used in verification emails Impact The vulnerability is a high severity one. Anyone using Django REST Registration library versions 0.2. - 0.4. with e-mail verification option (which is recommended, but needs additional configuration) is affected. In the worst case, the attacker can take over any Django user by resetting his/her password without even receiving the reset password verification link, just by guessing the signature from publicly available data (more detailed description below). Patches The problem has been patched in version 0.5.0. All library users should upgrade to version 0.5.0 or higher. The fix will invalidate all previously generated signatures , and in consequence, all verification links in previously sent verification e-mails. Therefore semi-major version 0.5.0 was released instead of version 0.4.6 to mark that incompatibility. Workarounds The easiest way way is to disable the verification options by…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-p3w6-jcg4-52xh
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-p3w6-jcg4-52xh
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2019-13177 Advisory: Improper Verification of Cryptographic Signature in django-rest-registration IDs: CVE-2019-13177, GHSA-p3w6-jcg4-52xh Record: https://patchnext.com/advisories/cve-2019-13177 (revision 3, source checked 26 Oct 2026, 13:17 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: django-rest-registration 0.5.0. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI django-rest-registration: affected >= 0.2.0, < 0.5.0; fixed in 0.5.0 ## Suggested inspection (read-only) - `python -m pip show django-rest-registration`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on django-rest-registration. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-p3w6-jcg4-52xh (OSV record GHSA-p3w6-jcg4-52xh lists affected ranges: PyPI django-rest-registration >=0.2.0 <0.5.0 (fixed)) - Verified: https://github.com/advisories/GHSA-p3w6-jcg4-52xh (GitHub-reviewed advisory GHSA-p3w6-jcg4-52xh lists affected ranges: PyPI django-rest-registration >=0.2.0 <0.5.0) Commands are suggestions: review each one before running it.
Loading voting…