Skip to content

Refresh may download untrusted builds of refresh-web

Moderate
jvyden published GHSA-vw8j-4jf6-rrqw May 23, 2024

Package

No package listed

Affected versions

< v2.11.3

Patched versions

2.11.4

Description

Summary

Whenever Refresh gets a new release it will use the latest artifact available of refresh-web. The branch to download from is not specified and if a PR is submitted at the right moment during a release, Refresh will download artifacts for actions (if the action is approved to run). This could potentially lead to many things, mainly that anyone can modify the website hosted on lbp.littlebigreresh.com to whatever they wish (if the timing's right and Refresh uses that artifact).

In practice, the outcome is fairly minor as there must be human review before workflows can run on pull requests and malicious code would probably be before workflows are approved.

I've seen this happen already when I published a pull request that made a change to how categories are presented. I noticed that my change was already in effect on the official Refresh instance before my pull request was even reviewed.

Solution

Specify the master branch in the artifact download job: LittleBigRefresh/Refresh@f6ffaab

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

CVE ID

No known CVE

Weaknesses

No CWEs

Credits