Skip to content

Path traversal in relay shared-files API

Low
amousset published GHSA-jjfq-p8xw-53g2 Sep 6, 2023

Package

rudder-relay (rudder)

Affected versions

>= 7.3.0, < 7.3.5
< 7.2.10

Patched versions

7.3.5
7.2.10
rudder-server-relay (rudder)
*
None

Description

Impact

It is possible to test for existence and compare hash of the file content to a hash for a file outside the shared folder by exploiting a path traversal in a HEAD request on the shared-folder API.

curl --head -v "http://127.0.0.1:3030/rudder/relay-api/1/shared-folder/%2e%2e%2f/etc/passwd" 

The impact is very limited as:

  • The GET endpoint is not affected, so it does not allow accessing the file content
  • The HEAD answer of this API does not give file size, but only compares content to a provided hash
  • It only works for files the rudder-relayd user on the system has access to
  • This request is only allowed locally or from an accepted node, managed by the target relay

Patches

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
High
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:H/UI:N/S:U/C:L/I:N/A:N

CVE ID

No known CVE

Weaknesses