Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2020-15128 | First vendor Publication | 2020-07-31 |
Vendor | Cve | Last vendor Modification | 2022-04-25 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N | |||
---|---|---|---|
Overall CVSS Score | 6.3 | ||
Base Score | 6.3 | Environmental Score | 6.3 |
impact SubScore | 4 | Temporal Score | 6.3 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Network | Attack Complexity | High |
Privileges Required | Low | User Interaction | None |
Scope | Changed | Confidentiality Impact | None |
Integrity Impact | High | Availability Impact | None |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : (AV:N/AC:M/Au:S/C:N/I:P/A:N) | |||
---|---|---|---|
Cvss Base Score | 3.5 | Attack Range | Network |
Cvss Impact Score | 2.9 | Attack Complexity | Medium |
Cvss Expoit Score | 6.8 | Authentication | Requires single instance |
Calculate full CVSS 2.0 Vectors scores |
Detail
In OctoberCMS before version 1.0.468, encrypted cookie values were not tied to the name of the cookie the value belonged to. This meant that certain classes of attacks that took advantage of other theoretical vulnerabilities in user facing code (nothing exploitable in the core project itself) had a higher chance of succeeding. Specifically, if your usage exposed a way for users to provide unfiltered user input and have it returned to them as an encrypted cookie (ex. storing a user provided search query in a cookie) they could then use the generated cookie in place of other more tightly controlled cookies; or if your usage exposed the plaintext version of an encrypted cookie at any point to the user they could theoretically provide encrypted content from your application back to it as an encrypted cookie and force the framework to decrypt it for them. Issue has been fixed in build 468 (v1.0.468). |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15128 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-327 | Use of a Broken or Risky Cryptographic Algorithm (CWE/SANS Top 25) |
CPE : Common Platform Enumeration
Type | Description | Count |
---|---|---|
Application | 5 |
Sources (Detail)
Alert History
Date | Informations |
---|---|
2022-04-25 21:23:31 |
|
2021-05-04 13:45:58 |
|
2021-04-22 02:57:46 |
|
2020-08-04 05:22:55 |
|
2020-08-01 00:22:54 |
|