Skip to content
Fencer Intel
medium —

GHSA-p799-q2pr-6mxj json

go.rgst.io/stencil/v2 vulnerable to Path Traversal

published last yr. modified 8mo ago also GO-2025-3584

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

### Impact

The library used to extract archives (github.com/jaredallard/archives) was vulnerable to the "zip slip" vulnerability. This is used to extract native extension archives and repository source archives. A native extension or repository archive could be crafted in such a way where a remote code execution or modification/reading of a file is possible using the user who is running stencil.

The severity is marked as "medium" because native extensions have always considered to be "unsafe" to run when not trusted. Native extensions are arbitrary code being ran, which could always do this same exploit with less steps. The medium severity is to reflect that this could be done even when a user is _not_ using a native extension, for example a repository source archive. However, one would need to mutate the archives provided by Github or perform some hackery with links, which may not be possible. Thus, "medium" is used out of an abundance of caution where I would've labeled this as "low".

### Patches

Patched in 2.3.0 and above.

### Workarounds

No workarounds are present.

### References

https://github.com/jaredallard/archives/security/advisories/GHSA-j95m-rcjp-q69h

Patch / fix

  • go go.rgst.io/stencil/v2 2.3.0

Is GHSA-p799-q2pr-6mxj 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
go go.rgst.io/stencil/v2
<2.3.0
2.3.0
go go.rgst.io/stencil
all versions
 no fix listed

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

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.