Skip to content

Uncovering memory corruption in NVIDIA Triton (as a new hire... #1241

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

carlospolop
Copy link
Collaborator

🤖 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:

semgrep --metrics=off --config=~/public-semgrep-rules/ --sarif > analysis.sarif

This flagged unsafe alloca() usage in http_server.cc and sagemaker_server.cc. Manual r...

🔧 Technical Details

An attacker can trigger a stack-based overflow in Triton by abusing evbuffer_peek and alloca(). By sending many minimal HTTP chunks ("1\r\nA\r\n"), libevent fragments the request into an unbounded number of evbuffer segments (n), causing alloca(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:

  1. Updated 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

  • Content is technically accurate
  • Formatting follows HackTricks style guidelines
  • Links and references are working
  • Content adds educational value
  • No sensitive information is exposed

This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.

@carlospolop
Copy link
Collaborator Author

🔗 Additional Context

Original Blog Post: https://blog.trailofbits.com/2025/08/04/uncovering-memory-corruption-in-nvidia-triton-as-a-new-hire/

Content Categories: Based on the analysis, this content was categorized under "generic-hacking/memory-corruption-stack-overflow.md".

Repository Maintenance:

  • MD Files Formatting: 865 files processed

Review Notes:

  • This content was automatically processed and may require human review for accuracy
  • Check that the placement within the repository structure is appropriate
  • Verify that all technical details are correct and up-to-date
  • All .md files have been checked for proper formatting (headers, includes, etc.)

Bot Version: HackTricks News Bot v1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant