liangliangyy DjangoBlog Setting settings.py hard-coded credentials
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.323% 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 security flaw has been discovered in liangliangyy DjangoBlog up to 2.1.0.0. This affects an unknown function of the file djangoblog/settings.py of the component Setting Handler. The manipulation of the argument SECRET_KEY results in hard-coded credentials. The attack can be launched remotely. The attack requires a high level of complexity. The exploitability is reported as difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way. | |
| Title | liangliangyy DjangoBlog Setting settings.py hard-coded credentials | |
| Weaknesses | CWE-259 CWE-798 |
|
| References |
| |
| Metrics |
cvssV2_0
|