Fixes an issue where the returned section data length is always 4 bytes larger than the actual section length. This could cause an issue where the caller accesses the final 4 bytes which would be invalid.
[x] Breaking change?
[ ] Impacts security?
[ ] Includes tests?
Marked as a breaking change due to modifying the behavior for the
library API.
How This Was Tested
CI
Verified size returned now matches the SectionData length
Integration Instructions
Review code to determine if FvLib is being used
If so, check if the FfsFindSectionData() API is being used
If so, check usage of the SectionDataSize parameter in code
to determine if a change needs to be made for the header size
being removed from the size returned.
Description
Fixes an issue where the returned section data length is always 4 bytes larger than the actual section length. This could cause an issue where the caller accesses the final 4 bytes which would be invalid.
How This Was Tested
SectionDatalengthIntegration Instructions
FvLibis being usedFfsFindSectionData()API is being usedSectionDataSizeparameter in code to determine if a change needs to be made for the header size being removed from the size returned.