Validate spell IDs after deserializing item save data#8631
Open
Santaingamba wants to merge 1 commit into
Open
Conversation
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
1 participant
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
Validate
item._iSpellimmediately after deserializing it inLoadItemData().If the loaded spell ID is invalid, it is replaced with
SpellID::Nullbefore it can be used by the rest of the codebase.Motivation
Issue #8547 reports that an invalid spell ID loaded from save data can later be passed to
GenerateStaffNameMagical(), resulting in an out-of-bounds access to the spell data table.Validating the value at the deserialization boundary prevents invalid spell IDs from propagating further.
Closes #8547.