fix: the strcpy call at runtime/memory/memory in memory.c#446
Merged
nicolasmd87 merged 1 commit intoMay 11, 2026
Merged
Conversation
Automated security fix generated by Orbis Security AI
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Fix critical severity security issue in
runtime/memory/memory.c.Vulnerability
V-001runtime/memory/memory.c:143Description: The strcpy call at runtime/memory/memory.c:143 copies a string into a destination buffer without any bounds checking. strcpy performs no length validation and will write past the end of the destination buffer if the source string is longer than the allocated space, corrupting adjacent heap or stack memory. This is a classic CWE-120 'Buffer Copy Without Checking Size of Input' vulnerability.
Changes
runtime/memory/memory.cVerification
Automated security fix by OrbisAI Security