Repository navigation
docs(security): verify the parsing-and-validation page - #321
Merged
Merged
Conversation
This was referenced Nov 3, 2026
homer6
force-pushed
the
security/293-object-representation
branch
from
November 3, 2026 12:23
11ecf8f to
b8810a8
Compare
homer6
force-pushed
the
security/294-parsing
branch
from
November 3, 2026 12:23
b92c5e5 to
b1b6853
Compare
homer6
changed the base branch from
security/293-object-representation
to
dev
November 3, 2026 12:47
Owner
Author
|
Merged into
|
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.
Verifies
docs/security/parsing-and-validation.md(#294). Stacked on #320.What the page now says
parse_portwithfrom_chars, checking the error, full consumption and the domain.from_charsrejects+, leading whitespace and-for unsigned.compile-failstd::format(user_text), which both compilers reject because the format string must be a constant, plus the right form.runtime_format/vformatonly for program-controlled strings. The same rule for SQL and processes.std::regexcautions: ReDoS, and libstdc++ before GCC 16 recursing on long input (GCC bug 86164, made iterative in GCC 16 by r16-7193). Mature parsers, tracked.Tests:
tests/security/parsing-and-validation_test.cpp, 5 tests:parse_portagainst 11 inputs, including an embedded NUL, signs, whitespace, overflow and the domain edges;format_error;Tested
securityarea: gcc-15 36/36, clang-22 36/36.compile-failpattern covers both compilers' consteval wording.Status: verified. README.md and CLAUDE.md need no change.
Related to #294, #286