How severe is GHSA-qmfx-75ff-8mw6?

No CVSS score has been assigned to GHSA-qmfx-75ff-8mw6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qmfx-75ff-8mw6?

GHSA-qmfx-75ff-8mw6 affects the following packages: github.com/ThomasLeister/prosody-filer (Go). Ecosystems affected: Go.

How do I fix GHSA-qmfx-75ff-8mw6?

Update github.com/ThomasLeister/prosody-filer to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qmfx-75ff-8mw6 is resolved across your whole dependency graph.

How do I detect GHSA-qmfx-75ff-8mw6 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ThomasLeister/prosody-filer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-qmfx-75ff-8mw6 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.

How does O3 Security protect against GHSA-qmfx-75ff-8mw6?

O3 pinpoints whether GHSA-qmfx-75ff-8mw6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-qmfx-75ff-8mw6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qmfx-75ff-8mw6 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-qmfx-75ff-8mw6 published, and has it been updated?

GHSA-qmfx-75ff-8mw6 was published on May 27, 2021 and was last updated on August 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-qmfx-75ff-8mw6

GHSA-qmfx-75ff-8mw6 is a security vulnerability in github.com/ThomasLeister/prosody-filer. O3 Security confirms whether GHSA-qmfx-75ff-8mw6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Listing of upload directory contents possible

Also known asGO-2022-0407

Published

May 27, 2021

Updated

Aug 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 21, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/ThomasLeister/prosody-filer

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

Description

There's an security issue in prosody-filer versions < 1.0.1 which leads to unwanted directory listings of download directories.

An attacker is able to list previous uploads of a certain user by shortening the URL and accessing a URL subdirectors other than /upload/ (or the corresponding user defined root dir)

Version 1.0.1 and later fix this problem and allow only direct file access if the full path is known. Directory listings are blocked entirely.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/ThomasLeister/prosody-filer`	all versions	1.0.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ThomasLeister/prosody-filer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/ThomasLeister/prosody-filer to 1.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qmfx-75ff-8mw6 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.
How O3 protects you
O3 pinpoints whether GHSA-qmfx-75ff-8mw6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qmfx-75ff-8mw6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

There's an security issue in prosody-filer versions **< 1.0.1** which leads to unwanted directory listings of download directories. An attacker is able to list previous uploads of a certain user by shortening the URL and accessing a URL subdirectors other than `/upload/` (or the corresponding user defined root dir) Version 1.0.1 and later fix this problem and allow only direct file access if the full path is known. Directory listings are blocked entirely.

O3 Security · Impact-Aware SCA

Is GHSA-qmfx-75ff-8mw6 in your dependencies?

O3 detects GHSA-qmfx-75ff-8mw6 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works