Bug 1478016 - samba: SMBLoris DoS attack on SMB service
Summary: samba: SMBLoris DoS attack on SMB service
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1478017 1478341 1478471 1478472 1478473 1478474 1478475 1478476 1478567
Blocks: 1478023
TreeView+ depends on / blocked
Reported: 2017-08-03 13:06 UTC by Adam Mariš
Modified: 2019-09-29 14:18 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-09-01 10:26:44 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Samba Project 12945 None None None 2019-07-20 09:19:21 UTC

Description Adam Mariš 2017-08-03 13:06:57 UTC
Samba is vulnerable to SMBLoris vulnerability affecting SMB service causing userspace OOM on Linux.





Comment 1 Adam Mariš 2017-08-03 13:07:37 UTC
Created samba tracking bugs for this issue:

Affects: fedora-all [bug 1478017]

Comment 2 Andreas Schneider 2017-08-03 16:15:57 UTC
max smbd processes (G)

    This parameter limits the maximum number of smbd(8) processes concurrently
    running on a system and is intended as a stopgap to prevent degrading
    service to clients in the event that the server has insufficient resources
    to handle more than this number of connections. Remember that under normal
    operating conditions, each user will have an smbd(8) associated with him or
    her to handle connections to all shares from a given host.

        Default: max smbd processes = 0

        Example: max smbd processes = 1000

Comment 3 Siddharth Sharma 2017-08-04 08:32:05 UTC

1. use 'max smb processes = <max number of processes allowed>' in /etc/samba/smb.conf to limit maximum number of smbd processes.

2. Limit the exposure of TCP port 445 to internet.

Comment 11 Huzaifa S. Sidhpurwala 2017-08-08 15:38:56 UTC
External Reference:


Comment 12 Huzaifa S. Sidhpurwala 2017-09-01 10:22:23 UTC

There is currently no upstream patch for this issue. The Red Hat Product Security Team advises customer to use the "Mitigation" provided, to resolve this security flaw. We shall revisit this issue, when an appropriate upstream patch is available.

Note You need to log in before you can comment on or make changes to this bug.