Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2019-9947 | First vendor Publication | 2019-03-23 |
| Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N | |||
|---|---|---|---|
| Overall CVSS Score | 6.1 | ||
| Base Score | 6.1 | Environmental Score | 6.1 |
| impact SubScore | 2.7 | Temporal Score | 6.1 |
| Exploitabality Sub Score | 2.8 | ||
| Attack Vector | Network | Attack Complexity | Low |
| Privileges Required | None | User Interaction | Required |
| Scope | Changed | Confidentiality Impact | Low |
| Integrity Impact | Low | Availability Impact | None |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : (AV:N/AC:M/Au:N/C:N/I:P/A:N) | |||
|---|---|---|---|
| Cvss Base Score | 4.3 | Attack Range | Network |
| Cvss Impact Score | 2.9 | Attack Complexity | Medium |
| Cvss Expoit Score | 8.6 | Authentication | None Required |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.3. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the path component of a URL that lacks a ? character) followed by an HTTP header or a Redis command. This is similar to the CVE-2019-9740 query string issue. This is fixed in: v2.7.17, v2.7.17rc1, v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1, v3.5.8, v3.5.8rc1, v3.5.8rc2, v3.5.9; v3.6.10, v3.6.10rc1, v3.6.11, v3.6.11rc1, v3.6.12, v3.6.9, v3.6.9rc1; v3.7.4, v3.7.4rc1, v3.7.4rc2, v3.7.5, v3.7.5rc1, v3.7.6, v3.7.6rc1, v3.7.7, v3.7.7rc1, v3.7.8, v3.7.8rc1, v3.7.9. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9947 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-93 | Failure to Sanitize CRLF Sequences ('CRLF Injection') |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2024-11-28 13:37:17 |
|
| 2024-08-02 13:10:17 |
|
| 2024-08-02 01:20:29 |
|
| 2024-02-02 02:11:16 |
|
| 2024-02-01 12:19:13 |
|
| 2023-12-09 13:00:27 |
|
| 2023-11-07 21:40:17 |
|
| 2023-09-05 13:05:48 |
|
| 2023-09-05 01:18:52 |
|
| 2023-09-02 13:04:42 |
|
| 2023-09-02 01:19:09 |
|
| 2023-08-22 12:57:59 |
|
| 2022-10-11 01:18:22 |
|
| 2022-08-16 17:27:44 |
|
| 2021-05-04 13:43:33 |
|
| 2021-04-22 02:55:35 |
|
| 2021-02-04 17:22:46 |
|
| 2021-01-07 12:28:36 |
|
| 2020-11-03 05:22:50 |
|
| 2020-09-03 01:28:59 |
|
| 2020-07-15 17:22:47 |
|
| 2020-07-10 12:25:18 |
|
| 2020-05-23 02:34:35 |
|
| 2019-09-19 12:03:16 |
|
| 2019-09-11 12:04:33 |
|
| 2019-08-07 12:11:00 |
|
| 2019-07-23 12:02:42 |
|
| 2019-06-26 12:10:17 |
|
| 2019-06-25 12:10:49 |
|
| 2019-06-21 12:10:10 |
|
| 2019-05-29 00:19:04 |
|
| 2019-05-27 12:01:11 |
|
| 2019-05-22 21:19:19 |
|
| 2019-05-17 09:18:25 |
|
| 2019-05-08 12:09:44 |
|
| 2019-04-26 12:09:47 |
|
| 2019-04-04 17:19:29 |
|
| 2019-03-26 17:19:15 |
|
| 2019-03-24 00:18:55 |
|
