fix(socks5): enforce authenticated state before CONNECT#5097
Merged
mcollina merged 1 commit intonodejs:mainfrom Apr 24, 2026
Merged
fix(socks5): enforce authenticated state before CONNECT#5097mcollina merged 1 commit intonodejs:mainfrom
mcollina merged 1 commit intonodejs:mainfrom
Conversation
Assisted-by: openai:gpt-5.4 Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5097 +/- ##
=======================================
Coverage 93.13% 93.13%
=======================================
Files 110 110
Lines 35816 35826 +10
=======================================
+ Hits 33356 33368 +12
+ Misses 2460 2458 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
This relates to...
Fixes: #5096
Rationale
Socks5Clientemitted'authenticated'on successful handshake/authentication but never transitioned into an authenticated state. As a result,connect()only rejected the already-connected state and could write a SOCKSCONNECTframe from invalid states such asinitial,handshaking,authenticating,closed, orerror.This also affected
Socks5ProxyAgent, which checkssocks5Client.state === 'authenticated'in theNO_AUTHflow. Since that state was never set, the agent could miss the already-emitted'authenticated'event and wait until the authentication timeout.Changes
AUTHENTICATEDstate toSocks5ClientAUTHENTICATEDbefore emitting'authenticated'in both auth-success pathsSocks5Client.connect()unless the client is authenticatedSocks5ProxyAgentto checkSTATES.AUTHENTICATEDFeatures
N/A
Bug Fixes
Socks5Client.connect()from sendingCONNECTbefore authentication completesSocks5Client.connect()from sendingCONNECTafter invalid lifecycle statesSocks5ProxyAgent’sNO_AUTHauthentication readiness check to use the actual authenticated stateBreaking Changes and Deprecations
This changes the internal
Socks5Client.statevalue after successful authentication from the previous implicit/incorrect behavior to an explicitauthenticatedstate.Socks5Clientis not part of the public top-levelundiciAPI, so there is no intended public API break.Status
Assisted-by: openai:gpt-5.4