Kiwi TCMS before 17.1 Hard-coded Django SECRET_KEY in Default Settings
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Kiwi TCMS | Kiwi TCMS | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Kiwi TCMS before 17.1 contains a hard-coded cryptographic key vulnerability that allows remote attackers to forge signed data by using the publicly known Django SECRET_KEY in tcms/settings/common.py. Attackers can forge or tamper with signed cookie-based messages and django.core.signing payloads, weakening password-reset and session-authentication HMACs on deployments keeping the default. | |
| Title | Kiwi TCMS before 17.1 Hard-coded Django SECRET_KEY in Default Settings | |
| First Time appeared |
Kiwitcms
Kiwitcms kiwi Tcms |
|
| Weaknesses | CWE-321 | |
| CPEs | cpe:2.3:a:kiwitcms:kiwi_tcms:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Kiwitcms
Kiwitcms kiwi Tcms |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Use of Hard-coded Cryptographic Key
No data.
No data.
No data.
No data.