STIGQter: STIG Summary: VMware vSphere 6.7 RhttpProxy Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 09 Mar 2021:

The rhttproxy must exclusively use the HTTPS protocol for client connections.

DISA Rule

SV-240723r679682_rule

Vulnerability Number

V-240723

Group Title

SRG-APP-000315-WSR-000003

Rule Version

VCRP-67-000008

Severity

CAT II

CCI(s)

• CCI-002314 - The information system controls remote access methods.

Weight

10

Fix Recommendation

Navigate to and open /etc/vmware-rhttpproxy/config.xml.

Locate the first <ssl> block and set its content to the following:

<ssl>
<!-- The server private key file -->
<privateKey>/etc/vmware-rhttpproxy/ssl/rui.key</privateKey>
<!-- The server side certificate file -->
<certificate>/etc/vmware-rhttpproxy/ssl/rui.crt</certificate>
<!-- vecs server name. Currently vecs runs on all node types. -->
<vecsServerName>localhost</vecsServerName>
</ssl>

Restart the service for changes to take effect.

# vmon-cli --restart rhttpproxy

Check Contents

At the command prompt, execute the following command:

# xmllint --xpath '/config/ssl' /etc/vmware-rhttpproxy/config.xml

Expected result:

<ssl>
<!-- The server private key file -->
<privateKey>/etc/vmware-rhttpproxy/ssl/rui.key</privateKey>
<!-- The server side certificate file -->
<certificate>/etc/vmware-rhttpproxy/ssl/rui.crt</certificate>
<!-- vecs server name. Currently vecs runs on all node types. -->
<vecsServerName>localhost</vecsServerName>
</ssl>

If the output does not match the expected result, this is a finding.

Vulnerability Number

V-240723

Documentable

False

Rule Version

VCRP-67-000008

Severity Override Guidance

At the command prompt, execute the following command:

# xmllint --xpath '/config/ssl' /etc/vmware-rhttpproxy/config.xml

Expected result:

<ssl>
<!-- The server private key file -->
<privateKey>/etc/vmware-rhttpproxy/ssl/rui.key</privateKey>
<!-- The server side certificate file -->
<certificate>/etc/vmware-rhttpproxy/ssl/rui.crt</certificate>
<!-- vecs server name. Currently vecs runs on all node types. -->
<vecsServerName>localhost</vecsServerName>
</ssl>

If the output does not match the expected result, this is a finding.

Check Content Reference

M

Target Key

5330

Comments