cve.bz

CVE-2021-32061 s3scanner project s3scanner: Path traversal

5.3 mediumEPSS 1.6%Fix available

Medium (5.3) in s3scanner project s3scanner. EPSS 1.6% estimated probability of exploitation activity in the next 30 days. Fixed in s3scanner 2.0.2.

On this page
S3Scanner before 2.0.2 allows Directory Traversal via a crafted bucket, as demonstrated by a <Key>../ substring in a ListBucketResult element.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
1.6% (unchanged from 1.6% a week ago; 1.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 77th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

  • s3scanner (PyPI): fixed in 2.0.2

Ask an AI about this CVE

Show the promptExplain CVE-2021-32061 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-32061?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-32061?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-32061 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
s3scanner_project:s3scannerbefore 2.0.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qppg-v75c-r5ffPyPIs3scanner<2.0.22.0.2
PYSEC-2021-433PyPIs3scanner<2.0.22.0.2

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON