Repository navigation
Fix PEM parsing resumption for empty labels - #135885
Merged
Merged
Conversation
|
Azure Pipelines: Successfully started running 3 pipeline(s). 13 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
|
Tagging subscribers to this area: @bartonjs, @vcsjones, @dotnet/area-system-security |
bartonjs
reviewed
Oct 15, 2026
bartonjs
approved these changes
Oct 15, 2026
Member
Author
|
/backport to release/10.0 |
Contributor
|
Started backporting to |
2 of 4 tasks
Member
Author
|
/backport to release/11.0 |
Contributor
|
Started backporting to |
2 of 4 tasks
This was referenced Oct 15, 2026
Closed
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
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.
In #133137 we fixed parsing to continue parsing at a more optimal location to prevent attempts to re-parse content that we know in advance is going to fail.
The fix advanced state a little too far in the narrow case of a PEM having an empty label. Consider the following PEM:
Initially, this is parsed as the PreEB:
-----BEGIN -----which is valid empty label. TheBEGIN TEST-----which immediately follows is invalid base64. Before this fix, it would attempt to resume parsing atBEGIN TEST-----\nZm9v\n-----END TEST-----. That wouldn't match because it resumed too far - it needs to resume where the "empty" label was initially found because the two PreEB's share a boundary.The same fix needs to be applied when looking for the end.
Fixes #135845