Skip to content
Fencer Intel
medium —

GHSA-m2xr-2vj4-wh94 json

tanton_engine has unsound public API

published last yr. modified last yr. also RUSTSEC-2025-0031

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

The following functions in the `tanton_engine` crate are unsound due to lack of sufficient boundary checks in public API:

- `Stack::offset()` - `ThreadStack::get()` - `RootMoveList::insert_score_depth()` - `RootMoveList::insert_score()`

The tanton_engine crate is no longer maintained, so there are no plans to fix this issue.

Is GHSA-m2xr-2vj4-wh94 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
crates.io tanton_engine
<=1.0.0
>=0.0.0-0
 no fix listed

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.