Merge Feature/v0.7.4p2 into main#39
Merged
Merged
Conversation
… size checks, truncation detection, guard cf consistency, security cookie validation, and seh table integrity
… directory. Added these expected heuristics to snapshot
…ctory. Added these expected heuristics to snapshot
…y. Added these expected heuristics to snapshot
…tory. Added these expected heuristics to snapshot
…. Added these expected heuristics to snapshot
…g directory. Added these expected heuristics to snapshot
…t testing documentation
…on, but lies beyond its declared virtual size -> out of bounds / gap, not in that section.
…SizeOfImage -> i.e. in the overlay.
…fuscators, and linkers et al.): A section claims to contain code (CNT_CODE) but is not executable (MEM_EXECUTE cleared). Clear contradictory state but the engine handles it as follows: a section marked CNT_CODE but lacking MEM_EXECUTE does not cause EP-related heuristics unless the EP actually lands inside it.
… not executable. This is real-world pattern used in malformed linkers, obfuscators, packers, intentionally broken binaries, fuzzing corpora. The engine behaviour: section name does not influence EP or section-validity heuristics - only characteristics do.
…uld choke on this given the non-ascii section name. IOCX normalises the name to an empty string and asserts: Non-ASCII section names must not break section parsing, and must be normalised to empty string with the appropriate anomaly heuristic. Note: This fixture would be a useful assertion if we later add section_name_non_ascii, section_name_invalid_encoding, section_name_high_bytes heuristics.
…l for normal software but perfectly valid in packers, self-modifying code, and anti-analysis tricks.
…rs deliberately misalign raw offsets to break naive parsers. Some malware loaders rely on Windows being more permissive than tools. Some exploit kits use misalignment to hide appended payloads or confuse RVA->RAW mapping. This contract asserts: Misaligned raw offsets do not break parsing and do not produce heuristics. If we later add section_raw_misaligned, this fixture will be valuable.
…ers. This fixture locks in the fact that the engine does not yet detect header overlap for abritrary sections.
…on is no longer diluting anomaly set
…Sizes handling to FixtureSpec and emitter, enabling adversarial cases where declared and actual directory counts differ. Optional header validator now checks raw vs declared counts as intended.
…. Changes include: 1. DOS stub now includes PAAXv1 provenance, 2. All fixtures generated deterministically via the new emitter pipelines, 3. Data directory table now fully populated (16 entries) where applicable
Collaborator
Author
|
Merging - v0.7.4 is fully validated, fixtures are green, performance improved, and all new directory/metadata logic is stable. |
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.
No description provided.