Skip to content
Fencer Intel
medium —

GHSA-mc9m-6fm9-pghc json

Zoo Design Studio: Memory-corruption in memory handling of lib-kcl

published 2mo ago modified 2mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

A race condition in kcl-lib can result in a use-after-free when accessing environments concurrently. During Vec reallocation, the previous buffer containing Box pointers is freed and replaced. A concurrent get_env operation that has already loaded a pointer to the old buffer may subsequently index into freed memory and retrieve a stale or corrupted Pin<Box<Environment>>.

Patch / fix

  • pypi zoo-kcl 0.3.153
  • crates.io kcl-lib 0.2.153

Is GHSA-mc9m-6fm9-pghc in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
pypi zoo-kcl
<0.3.153
0.3.153
crates.io kcl-lib
<0.2.153
0.2.153

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
  • CWE-416 Use After Free

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.