Improper Verification of Cryptographic Signature in scapy - #VU159476

 

Improper Verification of Cryptographic Signature in scapy - #VU159476

Published: November 5, 2026


Vulnerability identifier: #VU159476
CSH Severity: Medium
CVSS v4: 6 [CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N]
CVE-ID: N/A
CWE-ID: CWE-347
Exploitation vector: Adjecent network
Exploit availability: No public exploit available

Vulnerability details

The vulnerability allows an on-path network attacker to bypass required SMB signing in Scapy's SMB server and execute unsigned file operations within an authenticated session without possessing the session key. The demonstrated attack connected to a configured share, opened a file, and retrieved its contents using a replayed SMB Kerberos token and unsigned requests.

The vulnerability exists due to direction confusion in SMBStreamSocket.recv(), which applies client-side response signature-verification exemptions to inbound client requests even when SigningRequired is enabled and verification uses IsClient=False. Verification is skipped when the header carries Status=STATUS_PENDING, when MID is 0xFFFFFFFFFFFFFFFF, or when the command is ECHO. The status and message-ID exemptions concern incoming server responses, not client requests. A remote attacker can capture and replay a service token from an on-path position and inject unsigned requests carrying STATUS_PENDING into a session on a server configured with a share and an authentication provider. No later serving state rejects the requests after signature verification is bypassed.

Scapy's SMB_Server automaton uses SMBStreamSocket to parse incoming DirectTCP streams before dispatching requests to serving states. Configuring an authentication provider makes the server require signing to protect authenticated requests against alteration. In the reproduction, unsigned TREE_CONNECT, CREATE, and READ requests carrying STATUS_PENDING succeeded, while otherwise equivalent unsigned requests carrying a success status were rejected. The READ action then opened the configured path and returned its bytes. The relevant request-verification logic is in scapy/layers/smb2.py, and the file-serving logic is in scapy/layers/smbserver.py.


Affected software

scapy

Remediation

Install security update from vendor's website.

scapy - update to 2.8.0

External References

Related Security Bulletins