Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

GHSA-5mv2-rx3q-4w2v

HIGHFix: twigphp/Twig@22b9dc3

GHSA-5mv2-rx3q-4w2v is a high-severity (CVSS 8.8) CWE-74 vulnerability in twig/twig. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-5mv2-rx3q-4w2v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Code injection in Twig

Also known asCVE-2022-23614
Published
Feb 10, 2022
Updated
Feb 16, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
2 known
Exploitation data as of Feb 16, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
🐘twig/twig🐘twig/twig

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

Description

Description

When in a sandbox mode, the arrow parameter of the sort filter must be a closure to avoid attackers being able to run arbitrary PHP functions.

Resolution

We now disallow calling non Closure in the sort filter like we already did for some other filters.

Credits

We would like to thank Marlon Starkloff for reporting the issue and Fabien Potencier for fixing the issue.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagisttwig/twig2.0.0&&< 2.14.112.14.11
🐘Packagisttwig/twig3.0.0&&< 3.3.83.3.8
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 twig/twig. 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 twig/twig to 2.14.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5mv2-rx3q-4w2v 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-5mv2-rx3q-4w2v 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-5mv2-rx3q-4w2v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# Description When in a sandbox mode, the `arrow` parameter of the `sort` filter must be a closure to avoid attackers being able to run arbitrary PHP functions. # Resolution We now disallow calling non Closure in the `sort` filter like we already did for some other filters. # Credits We would like to thank Marlon Starkloff for reporting the issue and Fabien Potencier for fixing the issue.
O3 Security · Impact-Aware SCA

Is GHSA-5mv2-rx3q-4w2v in your dependencies?

O3 detects GHSA-5mv2-rx3q-4w2v across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-5mv2-rx3q-4w2v: Code injection in… | O3 Security