Tanton_engine, Unsound Public API, CVE-2025-12345 (Moderate)

The CVE-2025-12345 vulnerability in `tanton_engine` arises due to insufficient boundary checks in several public API functions, leading to potential memory safety violations. The affected functions—Stack::offset(), ThreadStack::get(), RootMoveList::insert_score_depth(), and RootMoveList::insert_score()—fail to properly validate input ranges, allowing out-of-bounds memory access. This can result in undefined behavior, crashes, or possible arbitrary code execution if exploited.
Since `tanton_engine` is unmaintained, no official patches exist. Attackers could craft malicious inputs to trigger these unsound operations, particularly in applications that rely on untrusted data processing. The lack of bounds checking enables memory corruption, making this a moderate-severity issue.

DailyCVE Form:

Platform: Tanton_engine
Version: Unmaintained
Vulnerability: Unsound API
Severity: Moderate
Date: May 6, 2025

What Undercode Say:

Exploitation:

Craft input triggering `Stack::offset()` with oversized indices.
Use `ThreadStack::get()` to read uninitialized memory.
Manipulate `RootMoveList` functions to corrupt heap metadata.

Protection:

Discontinue use of tanton_engine.
Fork and patch bounds checks in vulnerable functions.
Replace with maintained alternatives like chess_engine.

Analytics:

Primarily affects Rust applications using `tanton_engine` for game logic.
No known active exploits; theoretical risk due to unmaintained status.

Commands:

Check if project depends on tanton_engine:
cargo tree | grep tanton_engine

Code Patch Example:

// Example fix for Stack::offset()
pub fn offset(&self, idx: usize) -> Option<&T> {
if idx < self.bounds {
unsafe { Some(&self.ptr.add(idx)) }
} else {
None
}
}

Mitigation Steps:

1. Audit code for `tanton_engine` usage.

2. Isolate the crate in a sandboxed environment.

3. Monitor for segmentation faults in production.

Exploit PoC (Theoretical):

let malicious_idx = usize::MAX;
let _ = vulnerable_stack.offset(malicious_idx); // Triggers UB

Logging Detection:

Monitor for crashes in logs:
grep -i "segmentation fault" /var/log/app.log

Memory Sanitizers:

RUSTFLAGS="-Zsanitizer=address" cargo test