Skip to content

sing-box vulnerable to improper authentication in the SOCKS inbound

Critical severity GitHub Reviewed Published Sep 25, 2023 in SagerNet/sing-box • Updated Nov 6, 2023

Package

gomod github.com/sagernet/sing (Go)

Affected versions

< 0.2.12-0.20230925092853-5b05b5c147d9

Patched versions

0.2.12-0.20230925092853-5b05b5c147d9
gomod github.com/sagernet/sing-box (Go)
< 1.4.5
>= 1.5.0-beta.1, < 1.5.0-rc.5
1.4.5
1.5.0-rc.5

Description

Impact

This vulnerability allows specially crafted requests to bypass authentication, affecting all SOCKS inbounds with user authentication.

Patches

Update to sing-box 1.4.5 or 1.5.0-rc.5 and later versions.

Workarounds

Don't expose the SOCKS5 inbound to insecure environments.

References

@nekohasekai nekohasekai published to SagerNet/sing-box Sep 25, 2023
Published by the National Vulnerability Database Sep 25, 2023
Published to the GitHub Advisory Database Sep 26, 2023
Reviewed Sep 26, 2023
Last updated Nov 6, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

EPSS score

0.105%
(44th percentile)

Weaknesses

CVE ID

CVE-2023-43644

GHSA ID

GHSA-r5hm-mp3j-285g

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.