GHSA-g4mx-q9vg-27p4 · 深刻度： medium · エコシステム： pip — urllib3's request body not stripped after redirect from 303 status changes request method to GET
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.
総合評価: CVE-2023-45803 は低リスク（31.7/100）。CVSS 深刻度は中。悪用される可能性が高い（EPSS 0.54%、41 パーセンタイル） 推奨対応: 悪用情報と EPSS の推移を監視し、必要に応じて優先度を見直してください。
リスクは変動します。再評価に基づき、本ページの表示内容を更新しています。
EPSS は日次で悪用されやすさの相対度合いを推定します。パーセンタイルは採点済み CVE の中での相対位置（高いほど相対的に深刻）を示します。
| # | 日付 | 旧 EPSS スコア | 新 EPSS スコア | Δ（新 − 旧） |
|---|---|---|---|---|
| 1 | 2026-06-15 | 0.05% | 0.54% | +0.49% |
| 2 | 2025-11-21 | 0.16% | 0.05% | -0.11% |
| 3 | 2025-11-18 | — | 0.16% | — |
EPSS の全履歴 （全 8 件）
この CVE の CVSS 指標。
| ベーススコア | バージョン | 深刻度 | ベクトル | 悪用しやすさ | 影響 | スコアの出典 |
|---|---|---|---|---|---|---|
| 4.2 | 3.1 | MEDIUM |
|
0.5 | 3.6 | [email protected] |
| 4.2 | 3.1 | MEDIUM |
|
0.5 | 3.6 | [email protected] |
GHSA-g4mx-q9vg-27p4 · 深刻度： medium · エコシステム： pip — urllib3's request body not stripped after redirect from 303 status changes request method to GET
| vendor | priority | summary | link |
|---|---|---|---|
alpine
|
medium | CVE-2023-45803: 1 source package rows (py3-urllib3); 22 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 15. | https://security.alpinelinux.org/vuln/CVE-2023-45803 |
debian
|
not yet assigned | CVE-2023-45803 not yet assigned priority: Debian including 1 source packages (python-urllib3), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. | https://security-tracker.debian.org/tracker/CVE-2023-45803 |
redhat
|
medium | — | https://access.redhat.com/security/cve/CVE-2023-45803 |
suse
|
medium | CVE-2023-45803 severity moderate: SUSE including 398 source package names (5.0.0-beta1.2.122:python3-urllib3-1.25.10-150300.4.9.1, 5.0.0-beta1.2.90:python3-urllib3-1.25.10-150300.4.9.1, …), 704 product×package rows across 311 product lines (Container bci/kiwi, Container suse/manager/4.3/proxy-tftpd, … (311 product lines)): Fixed 517, Known Affected 187. | https://www.suse.com/security/cve/CVE-2023-45803/ |
ubuntu
|
medium | CVE-2023-45803 medium priority: Ubuntu including 2 source packages (python-pip, python-urllib3), 24 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): released 14, not-affected 6, needed 2, ignored 1, needs-triage 1. | https://ubuntu.com/security/CVE-2023-45803 |