Skip to content

Violation of the integrity of file distribution

Moderate
psi-4ward published GHSA-xg8v-m2mh-45m6 Apr 5, 2024

Package

No package listed

Affected versions

< 2.1.2

Patched versions

2.2.0

Description

Difference from vulnerability number GHSA-2p2x-p7wj-j5h2

This vulnerability allows you to violate the integrity of a file bucket and upload new files there. Violation of integrity on the bucket. While the vulnerability with the number GHSA-2p2x-p7wj-j5h2 allows you to violate the integrity of a single file that is uploaded by another user by writing data there and not allows you to upload new files to the bucket. Thus, vulnerabilities are reproduced differently, require different security recommendations and affect different objects of the application’s business logic.

Summary
The absence of restrictions on the endpoint, which allows you to create a path for uploading a file in a file distribution, allows an attacker to add arbitrary files to the distribution.

Details
Vulnerable endpoint: POST /files

PoC

  1. Create a file distribution.
Снимок экрана 2024-03-17 в 21 27 30
  1. Go to the link address (id of the file distribution is needed by an attacker to upload files there).
Снимок экрана 2024-03-17 в 21 27 35
  1. Send a POST /files. As the value of the Upload-Metadata header we specify the sid parameter with the id of the file distribution obtained in the second step. In the response from the server in the Location header we get the path for uploading a new file to the file distribution.
Снимок экрана 2024-03-17 в 21 28 09
  1. Send a PATCH /files/{{id}} request with arbitrary content in the request body. Id is taken from the previous step.
Снимок экрана 2024-03-17 в 21 28 51

Result:
Снимок экрана 2024-03-17 в 21 29 05
Снимок экрана 2024-03-17 в 21 29 15

Impact
The vulnerability allows an attacker to influence those users who come to the file distribution after him and slip the victim files with a malicious or phishing signature.

Severity

Moderate

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
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
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:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

CVE ID

CVE-2024-31453

Weaknesses

No CWEs

Credits