How severe is GHSA-22wc-c9wj-6q2v?

No CVSS score has been assigned to GHSA-22wc-c9wj-6q2v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-22wc-c9wj-6q2v?

GHSA-22wc-c9wj-6q2v affects the following packages: vyper (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-22wc-c9wj-6q2v?

Update vyper to 0.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-22wc-c9wj-6q2v is resolved across your whole dependency graph.

How do I detect GHSA-22wc-c9wj-6q2v in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vyper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-22wc-c9wj-6q2v if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is GHSA-22wc-c9wj-6q2v actively exploited in the wild?

No public exploit code has been indexed for GHSA-22wc-c9wj-6q2v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-22wc-c9wj-6q2v published, and has it been updated?

GHSA-22wc-c9wj-6q2v was published on April 19, 2021 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

VVE-2021-0001: Memory corruption using function calls within arraysGHSA-22wc-c9wj-6q2v

Fix: vyperlang/vyper#2345

GHSA-22wc-c9wj-6q2v is a remote code execution vulnerability in vyper. A fix is available for vyper — see the affected versions and patch details below.

Published

Apr 19, 2021

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍vyper

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

Impact

When performing a function call inside an array, there is a memory corruption issue that occurs because of an incorrect pointer to the the tip of the stack.

Patches

This issue was partially fixed in VVE-2020-0004, however the fix did not update similar code for arrays, which had a similar issue. The issue is fully fixed in https://github.com/vyperlang/vyper/pull/2345

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`vyper`	all versions	0.2.12`pip install --upgrade 'vyper==0.2.12'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vyper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vyper to 0.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-22wc-c9wj-6q2v is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

### Impact When performing a function call inside an array, there is a memory corruption issue that occurs because of an incorrect pointer to the the tip of the stack. ### Patches This issue was partially fixed in [VVE-2020-0004](https://github.com/vyperlang/vyper/security/advisories/GHSA-2r3x-4mrv-mcxf), however the fix did not update similar code for arrays, which had a similar issue. The issue is fully fixed in https://github.com/vyperlang/vyper/pull/2345

O3 Security · Impact-Aware SCA

Is GHSA-22wc-c9wj-6q2v in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works