Homepage

Information Exposure Affecting container-tools:rhel8/oci-seccomp-bpf-hook package, versions <0:1.2.10-1.module+el8.10.0+20565+a40ba0e5

Severity

 Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.04% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-CONTAINERTOOLS-8158397
  • published2 Oct 2024
  • disclosed13 Oct 2023
Report a new vulnerability Found a mistake?

Introduced: 13 Oct 2023

CVE-2023-45803  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade RHEL:8 container-tools:rhel8/oci-seccomp-bpf-hook to version 0:1.2.10-1.module+el8.10.0+20565+a40ba0e5 or higher.
This issue was patched in RHSA-2024:2988.

NVD Description

Note: Versions mentioned in the description apply only to the upstream container-tools:rhel8/oci-seccomp-bpf-hook package and not the container-tools:rhel8/oci-seccomp-bpf-hook package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

urllib3 is a user-friendly HTTP client library for Python. urllib3 previously wouldn't remove the HTTP request body when an HTTP redirect response using status 301, 302, or 303 after the request had its method changed from one that could accept a request body (like POST) to GET as is required by HTTP RFCs. Although this behavior is not specified in the section for redirects, it can be inferred by piecing together information from different sections and we have observed the behavior in other major HTTP client implementations like curl and web browsers. Because the vulnerability requires a previously trusted service to become compromised in order to have an impact on confidentiality we believe the exploitability of this vulnerability is low. Additionally, many users aren't putting sensitive data in HTTP request bodies, if this is the case then this vulnerability isn't exploitable. Both of the following conditions must be true to be affected by this vulnerability: 1. Using urllib3 and submitting sensitive information in the HTTP request body (such as form data or JSON) and 2. The origin service is compromised and starts redirecting using 301, 302, or 303 to a malicious peer or the redirected-to service becomes compromised. This issue has been addressed in versions 1.26.18 and 2.0.7 and users are advised to update to resolve this issue. Users unable to update should disable redirects for services that aren't expecting to respond with redirects with redirects=False and disable automatic redirects with redirects=False and handle 301, 302, and 303 redirects manually by stripping the HTTP request body.

CVSS Scores

version 3.1