Bug 2225392 - Servers can expose an Rsync service on port 873
Summary: Servers can expose an Rsync service on port 873
Keywords:
Status: CLOSED DUPLICATE of bug 2219698
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 16.2 (Train)
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
: ---
Assignee: OSP Team
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-25 08:08 UTC by Ganesh Kadam
Modified: 2023-07-25 08:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-25 08:45:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-26872 0 None None None 2023-07-25 08:09:20 UTC

Description Ganesh Kadam 2023-07-25 08:08:17 UTC 
Description of problem:

Servers can expose an Rsync service on port 873. If no hardening is done, any user
with a network access to the machine will be able to access the different data
exposed by the Rsync service leading to important data leak
10.91.209.251:873 open tcp rsync
10.91.205.184:873 open tcp rsync

The RSync service is exposed by the two following machines:
• cirp11ospctlfb201.infra.eu-muc-11.cloud.amadeus.net
• cirp12ospctlfa201.infra.eu-muc-12.cloud.amadeus.net
The service is unauthenticated and exposes the following directories:
• accounts
• containers
• objects


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

How reproducible:
Always

Actual results:
Bydefault VM Servers can expose an Rsync service on port 873 leading to security vulnerablity

Expected results:
RSYNC should be configured on some other port other than its default port

Additional info:
Comment 2 Takashi Kajinami 2023-07-25 08:45:42 UTC 
This is duplicate of bz 2219698 .

*** This bug has been marked as a duplicate of bug 2219698 ***
Note You need to log in before you can comment on or make changes to this bug.