CVE-2023-31543
A public proof of concept exists; no exploitation attested.
- Published2023-06-30
- Fixed in0.4.12
- WeaknessCWE-427
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A dependency confusion in pipreqs v0.3.0 to v0.4.11 allows attackers to execute arbitrary code via uploading a crafted PyPI package to the chosen repository server.
Timeline
dates in UTC- 2023-06-3020:15CVE publishedNVD
Versions per branch
OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.x | ≥ 0.3.0, < 0.4.12 | 0.4.12 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 0.x | ≥ 0.3.0, ≤ 0.4.11 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- python-pipreqsopenSUSE:Tumbleweedall versions · fixed in 0.5.0-2.2
Fix
- Update pipreqs to 0.4.12
Advisories and patches
- gist.github.comMitigation
- github.comMitigation · Patch · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- CISA-ADP (SSVC)PoC stated2024-11-26
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- CISA-ADPSSVC decisionpoc2024-11-26
- NVDCVSS 3.19.8read 2026-10-23
- NVDweakness (CWE)CWE-427read 2026-10-23
- FIRST EPSSEPSS score1.2 %2026-11-18
- OSVaffected packages—
- GitHub AdvisoriesadvisoryCRITICAL2023-06-30
Identifiers
- EUVD-2023-0201same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-v4f4-23wc-99mhsame flawGitHub Advisory Database · CC-BY-4.0
- PYSEC-2023-99same flawPyPA Advisory Database · CC-BY-4.0
- openSUSE-SU-2026:12026-1advisory covering several CVEsopenSUSE · LicenseRef-unstated
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2023-06-30
- Last Modified
- 2026-06-17
- NVD status
- Modified
- GitHub Advisory
- GHSA-v4f4-23wc-99mh
Frequently asked questions
What is CVE-2023-31543?
Is CVE-2023-31543 actively exploited?
What is the CVSS score for CVE-2023-31543?
Running pipreqs? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-v4f4-23wc-99mh
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- CISA Vulnrichment · CC0-1.0