Uncovering memory corruption in NVIDIA Triton (as a new hire... #1241
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
Stack Allocation Vulnerabilities in NVIDIA Triton Inference Server (CVE-2025-23310 & CVE-2025-23311)
Background
During a 30-day onboarding at Trail of Bits, the author applied the following command to the Triton codebase:
This flagged unsafe
alloca()
usage inhttp_server.cc
andsagemaker_server.cc
. Manual r...🔧 Technical Details
An attacker can trigger a stack-based overflow in Triton by abusing
evbuffer_peek
andalloca()
. By sending many minimal HTTP chunks ("1\r\nA\r\n"
), libevent fragments the request into an unbounded number ofevbuffer
segments (n), causingalloca(sizeof(evbuffer_iovec) * n)
to allocate excessive stack memory and corrupt the stack.To systematically explore and exploit this condition, one can build Triton with debug symbols, ...
🤖 Agent Actions
Added a new real-world case study for stack-based overflows:
src/binary-exploitation/stack-overflow/README.md
• Added “CVE-2025-23310 & CVE-2025-23311 (NVIDIA Triton Inference Server)” section
• Detailed vulnerable
alloca()
pattern, chunked-encoding amplification, PoC exploit, and patch/mitigation• Highlighted key lessons for developers and reviewers
• Extended the References list with the Trail of Bits blog link
This integrates the new Triton memory-corruption technique into the existing Stack Overflow page, enriching HackTricks with another modern, real-world exploitation scenario.
✅ Review Checklist
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.