Skip to content

The "sharedfile_to_node" method does not verify the policy server's certificate with default configuration

Low
amousset published GHSA-2w5q-7g5h-x79h Sep 18, 2023

Package

rudder-agent (rudder)

Affected versions

>= 7.3.0, < 7.3.6
< 7.2.11

Patched versions

7.3.6
7.2.11
rudder-server (rudder)
>= 7.3.0, < 7.3.6
< 7.2.11
7.3.6
7.2.11
rudder-webapp (rudder)
*
None

Description

Impact

The sharedfile_to_node method uses the rudder_verify_certs_option variable (from the system techniques) as a parameter to curl. This is a leftover from Rudder 6.X certificate check configuration. As a consequence, it uses the value from the RUDDER_VERIFY_CERTIFICATES system variable which is described in the settings as only used for 6.X nodes compatibility. When the settings is set to false (which is its default value), an --insecure flag is passed to the curl call and the certificate is hence not checked.

This also affects the following plugins which use this method internally:

  • openscap
  • zabbix
  • centreon

The plugins use the method to send file to the root server, which means an attacker could get access to a list of monitoring roles for the nodes or OpenSCAP reports. This does not expose additional data nor give write access to anything.

Patches

To fix the bug, it is necessary to upgrade both the central Rudder server and the agents using the method.

Workarounds

None.

References

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CVE ID

No known CVE

Weaknesses