CVE-2018-18074
Public on
Last Modified:
Description
A credentials-exposure flaw was found in python-requests, where if a request with authentication is redirected (302) from an HTTPS endpoint to an HTTP endpoint on the same host, the Authorization header is not stripped and the credentials can be read in plain text. A man-in-the-middle attacker could exploit this flaw to obtain a user's valid credentials.
Additional Information
- This content is not included.Bugzilla 1643829: python-requests: Redirect from HTTPS to HTTP does not remove Authorization header
- Content from cwe.mitre.org is not included.CWE-522: Insufficiently Protected Credentials
- FAQ: Frequently asked questions about CVE-2018-18074
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2018-18074
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2018-18074
Affected Packages and Issued Red Hat Security Errata
| Products / Services | Components | State | Errata |
|---|---|---|---|
| Red Hat Ansible Tower 3.5 for RHEL 7 | ansible-tower-35/ansible-tower | Fixed | RHBA-2020:1539 |
| Red Hat Ansible Tower 3.6 for RHEL 7 | ansible-tower-36/ansible-tower | Fixed | RHBA-2020:1540 |
| Red Hat Enterprise Linux 6 | python-requests | Will not fix | |
| Red Hat Enterprise Linux 7 | python-requests | Fixed | RHSA-2019:2035 |
| Red Hat Enterprise Linux 7 | python-pip | Fixed | RHSA-2020:0850 |
| Red Hat Enterprise Linux 7 | python-virtualenv | Fixed | RHSA-2020:0851 |
| Red Hat Enterprise Linux 7 | python-pip | Fixed | RHSA-2020:2068 |
| Red Hat Enterprise Linux 7 | python-virtualenv | Fixed | RHSA-2020:2081 |
| Red Hat Enterprise Linux 8 | python36:3.6/python-virtualenv | Affected | |
| Red Hat Enterprise Linux 8 | python27:2.7 | Fixed | RHSA-2020:1605 |
| Red Hat Enterprise Linux 8 | python-pip | Fixed | RHSA-2020:1916 |
| Red Hat Enterprise Linux 8 | python-requests | Not affected | |
| Red Hat OpenShift Container Platform 3.9 | python-requests | Affected | |
| Red Hat OpenStack Platform 10 (Newton) | python-requests | Fix deferred | |
| Red Hat OpenStack Platform 12 (Pike) | python-requests | Affected | |
| Red Hat OpenStack Platform 13 (Queens) | python-requests | Fix deferred | |
| Red Hat OpenStack Platform 14 (Rocky) | python-requests | Affected | |
| Red Hat OpenStack Platform 8 (Liberty) | python-requests | Fix deferred | |
| Red Hat OpenStack Platform 9 (Mitaka) | python-requests | Fix deferred | |
| Red Hat Software Collections | python27-python-pip | Fix deferred | |
| Red Hat Software Collections | python27-python-virtualenv | Fix deferred | |
| Red Hat Software Collections | rh-mongodb36-python-requests | Fix deferred | |
| Red Hat Software Collections | rh-python36-python-pip | Fix deferred | |
| Red Hat Software Collections | rh-python36-python-virtualenv | Fix deferred | |
| Red Hat Storage 3 | python-requests | Fix deferred |
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).
| CVSS v3 Score Breakdown | Red Hat | NVD |
|---|---|---|
| CVSS v3 Base Score | 2.6 | 7.5 |
| Attack Vector | Adjacent Network | Network |
| Attack Complexity | High | Low |
| Privileges Required | None | None |
| User Interaction | Required | None |
| Scope | Unchanged | Unchanged |
| Confidentiality Impact | Low | High |
| Integrity Impact | None | None |
| Availability Impact | None | None |
CVSS v3 Vector
Red Hat CVSS:3.0/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
NVD CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
Not sure what something means? Check out our Security Glossary.