Vulnenv week9 - #10
Open
Nayeraneru wants to merge 3 commits into
Open
Conversation
|
gave it a quick look over, not much of a code review, and looks like a good iteration. i'll try to give it a run later |
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.
Refering to rapid7#20506
GSoC 2026 — Week 9 deliverables for the Automated Vulnerable Environment Provisioning project.
Summary
Closes the gap where
ci.validationwas defined in the schema but never actually checked. Addstest_env validate <ID>, making environment definitions a real single source of truth for pass/fail — not just for container config, health checks, and datastore, but for validation too.Changes
test_env validate <ID>command: resolves a built environment'sci.validationblock and checks the session it produced (type + expected output), printingPASS/FAILwith a specific reason.sys.config.getuid(TLV request/response) instead ofshell_command_token(process channel), after the latter proved unreliable in this environment. Shell sessions still useshell_command_token.wordpress.yml/activemq.yml: removed hardcodedLHOST: 127.0.0.1fromci.exploit.options— it broke callback connectivity from inside containers. Left unset so Metasploit's own interface auto-detection applies.ci.exploit/ci.validationfields, theLHOSTgotcha, and a known limitation —exec/validatemust run in the same msfconsole process, since sessions are process-local.deferred
Duplication reduction across multiple modules sharing one definition is architecturally supported but not demonstrated — currently one module per definition. Real proof needs a second module added to an existing definition, which fits better under Week 10
Testing Result: