liangliangyy DjangoBlog File Upload Endpoint settings.py hard-coded key
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| liangliangyy | DjangoBlog | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Liangliangyy | Djangoblog |
|
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.248% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Liangliangyy
Liangliangyy djangoblog |
|
| Vendors & Products |
Liangliangyy
Liangliangyy djangoblog |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A vulnerability was found in liangliangyy DjangoBlog up to 2.1.0.0. This affects an unknown function of the file djangoblog/settings.py of the component File Upload Endpoint. Performing a manipulation of the argument SECRET_KEY results in use of hard-coded cryptographic key . Remote exploitation of the attack is possible. The attack's complexity is rated as high. The exploitability is reported as difficult. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way. | |
| Title | liangliangyy DjangoBlog File Upload Endpoint settings.py hard-coded key | |
| Weaknesses | CWE-320 CWE-321 |
|
| References |
| |
| Metrics |
cvssV2_0
|