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.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2019-0033 | 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. |
Github GHSA |
GHSA-p3w6-jcg4-52xh | Improper Verification of Cryptographic Signature in django-rest-registration |
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-04T23:41:10.490Z
Reserved: 2019-07-02T00:00:00.000Z
Link: CVE-2019-13177
No data.
Status : Modified
Published: 2019-07-02T22:15:09.770
Modified: 2024-11-21T04:24:21.807
Link: CVE-2019-13177
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA