test(sip): M7 CP5 — origination signalling-scope analysis + regression (M6 MINOR-1)#161
Merged
Merged
Conversation
…n (M6 MINOR-1) Folds the M6 routing MINOR-1 ancillary-signalling-leak finding into an M7-scoped answer: which ancillary paths does a Chime origination actually exercise? Finding (README): NONE. AWS Chime Voice Connector termination is IP-authenticated (no outbound REGISTER); the origination path implements no transfer (no REFER), no subscription (no NOTIFY), no MESSAGE, and rustisk is the session-timer RESPONDER not refresher (no outbound UPDATE). The core INVITE (M6 CP2) and the in-dialog ACK/BYE/CANCEL (M7 CP1) already route through signaling_hostport()/advertised_signaling_hostport(), so the whole origination signalling path is already NAT-scoped. Scoping the genuinely ancillary paths (refer.rs/notify*.rs/messaging.rs/outbound_registration.rs/update.rs) is a real latent leak but OFF the M7 origination path — documented and deferred. Delivers a receiver-side regression (tests/cp5-origination-signaling-scope) that locks the origination scoping in: with external_signaling_address configured and the carrier outside local_net, the offline carrier asserts INVITE + ACK + BYE all advertise the external host and none leaks the raw 0.0.0.0 bind. Captured RED (CP5_MODE=red-noext): dropping external_signaling_address makes every request leak 0.0.0.0 -> assertion RED. No Rust changes.
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.
M7 CP5 — origination signalling-scope: analysis + regression (M6 routing MINOR-1)
Folds the M6 routing MINOR-1 finding (ancillary paths still emit the raw internal
bind) into an M7-scoped answer: which ancillary signalling paths does a Chime
origination actually exercise?
Finding: none
refresher=uacresponder, never originates a refreshThe core INVITE (M6 CP2) and the in-dialog ACK/BYE/CANCEL (M7 CP1) already route
through
signaling_hostport(), so the whole origination signalling path isNAT-scoped. Scoping the genuinely ancillary paths is a real latent leak but
off the M7 origination path — documented + deferred (see README).
Receiver-side regression that locks the scoping in
tests/cp5-origination-signaling-scope/run.sh— withexternal_signaling_address = signaling.example.netand the carrier outsidelocal_net:Captured RED (
CP5_MODE=red-noext)Drop
external_signaling_address→ every request leaks the raw bind:No Rust changes;
cargo test/clippyunaffected. Isolated Docker only.