fix(pdf): bound cross-reference parsing - #120
Merged
Merged
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
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.
What
startxref,/Prev, and/XRefStmchain with a hard hop limit/W,/Index,/Size, and PNG predictor row allocations before lopdf runsWhy
Malformed xref streams can otherwise trigger large allocations before the read-only text classifier reaches its existing object and content-stream limits.
Verification
cargo test --manifest-path src-tauri/Cargo.toml --lib(310 passed)cargo test --manifest-path src-tauri/Cargo.toml --lib source_content(55 passed)cargo clippy --lib --testscompleted; only existing repository warnings remainrustfmt --checkandgit diff --checkScope
Read-only classifier only: no command, UI, mutation, release, or
mainchanges. Bounded content-operator parsing remains a separate follow-up PR.Refs #33