How severe is GHSA-2gq2-m628-33xp?

No CVSS score has been assigned to GHSA-2gq2-m628-33xp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2gq2-m628-33xp?

GHSA-2gq2-m628-33xp affects the following packages: gregwar/rst (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2gq2-m628-33xp?

Update gregwar/rst to 1.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2gq2-m628-33xp is resolved across your whole dependency graph.

How do I detect GHSA-2gq2-m628-33xp in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gregwar/rst, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2gq2-m628-33xp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-2gq2-m628-33xp actively exploited in the wild?

No public exploit code has been indexed for GHSA-2gq2-m628-33xp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2gq2-m628-33xp published, and has it been updated?

GHSA-2gq2-m628-33xp was published on May 15, 2024 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

gregwar/rst Local File Inclusion Vulnerability

Real-World Exposure

1 pkg affected

🐘gregwar/rst

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

A Local File Inclusion (LFI) vulnerability has been discovered in the gregwar/rst library, potentially exposing sensitive files on the server to unauthorized users. The issue arises from inadequate input validation, allowing an attacker to manipulate file paths and include arbitrary files.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`gregwar/rst`	all versions	1.0.3`composer require gregwar/rst:^1.0.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gregwar/rst, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update gregwar/rst to 1.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2gq2-m628-33xp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

A Local File Inclusion (LFI) vulnerability has been discovered in the gregwar/rst library, potentially exposing sensitive files on the server to unauthorized users. The issue arises from inadequate input validation, allowing an attacker to manipulate file paths and include arbitrary files.

O3 Security · Impact-Aware SCA

Is GHSA-2gq2-m628-33xp in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works