Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

GHSA-7xc5-ggpp-g249

CRITICALFix: Gallopsled/pwntools#1732

GHSA-7xc5-ggpp-g249 is a critical-severity (CVSS 9.8) CWE-74 vulnerability in pwntools. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-7xc5-ggpp-g249 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

pwntools Server-Side Template Injection (SSTI) vulnerability

Also known asCVE-2020-28468PYSEC-2021-72SNYK-PYTHON-PWNTOOLS-1047345
Published
Apr 20, 2021
Updated
Oct 18, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Oct 18, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐍pwntools

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

This affects the package pwntools before 4.3.1. The shellcraft generator for affected versions of this module are vulnerable to Server-Side Template Injection (SSTI), which can lead to remote code execution.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIpwntoolsall versions4.3.1
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pwntools. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update pwntools to 4.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7xc5-ggpp-g249 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-7xc5-ggpp-g249 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7xc5-ggpp-g249. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This affects the package pwntools before 4.3.1. The shellcraft generator for affected versions of this module are vulnerable to Server-Side Template Injection (SSTI), which can lead to remote code execution.
O3 Security · Impact-Aware SCA

Is GHSA-7xc5-ggpp-g249 in your dependencies?

O3 detects GHSA-7xc5-ggpp-g249 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-7xc5-ggpp-g249: pwntools Remote… | O3 Security