Bug 1553274 - Restrict memcached on overcloud nodes to listen to tcp only
Summary: Restrict memcached on overcloud nodes to listen to tcp only
Keywords:
Status: CLOSED DUPLICATE of bug 1551182
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 10.0 (Newton)
Hardware: All
OS: All
medium
low
Target Milestone: ---
: ---
Assignee: Emilien Macchi
QA Contact: Gurenko Alex
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-08 15:41 UTC by Cody Swanson
Modified: 2022-08-16 10:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-19 20:15:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-4951 0 None None None 2022-08-16 10:58:10 UTC

Description Cody Swanson 2018-03-08 15:41:12 UTC
Description of problem: 

The overcloud memcached listens on both tcp and udp but the services that use memcached only seem to use tcp. We should restrict memcached to listen on tcp only to reduce attack surface and increase product security. 

Version-Release number of selected component (if applicable):

memcached-1.4.33-3.el7ost.x86_64

How reproducible:

Deploy overcloud using director, memcached listens on tcp and udp by default.  

Steps to Reproduce:

1. Deploy overcloud.

Actual results: 

memcached listens on tcp and udp while services only seem to communicate with it using tcp.

Expected results: 

memcached listens on tcp only.

Additional info: 

I've tested this in my lab and I did not notice any problems with restricting it. I monitored my running overcloud nodes for traffic on udp port 11211 and notice none over a few hours. 

[root@controller-0 ~]# cat /etc/sysconfig/memcached 
PORT="11211"
USER="memcached"
MAXCONN="8192"
CACHESIZE="15087"
OPTIONS="-l 172.17.1.19 -U 0 -t 4 >> /var/log/memcached.log 2>&1"

Comment 1 Alex Schultz 2018-03-19 20:15:55 UTC
This is getting resolved as part of the CVE-2018-1000115 mitigation.

*** This bug has been marked as a duplicate of bug 1551182 ***


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