How severe is GHSA-6r78-m64m-qwcf?

No CVSS score has been assigned to GHSA-6r78-m64m-qwcf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6r78-m64m-qwcf?

GHSA-6r78-m64m-qwcf affects the following packages: moq (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-6r78-m64m-qwcf?

Update moq to 4.20.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6r78-m64m-qwcf is resolved across your whole dependency graph.

How do I detect GHSA-6r78-m64m-qwcf in my NuGet dependencies?

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

How do I mitigate GHSA-6r78-m64m-qwcf 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-6r78-m64m-qwcf?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6r78-m64m-qwcf can be triaged on real exposure rather than presence alone.

Is GHSA-6r78-m64m-qwcf actively exploited in the wild?

No public exploit code has been indexed for GHSA-6r78-m64m-qwcf 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-6r78-m64m-qwcf published, and has it been updated?

GHSA-6r78-m64m-qwcf was published on August 10, 2023 and was last updated on December 1, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

Not in CISA KEV

GHSA-6r78-m64m-qwcf — moq

Fix: moq/moq#1363

GHSA-6r78-m64m-qwcf is a security vulnerability in moq. A fix is available for moq — see the affected versions and patch details below.

Moq v4.20.0-rc to 4.20.1 share hashed user data

Published

Aug 10, 2023

Updated

Dec 1, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 1, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

.NETmoq

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

Description

Moq v4.20.0-rc to 4.20.1 include support for SponsorLink, which runs an obfuscated DLL at build time that scans local git config data and shares the user's hashed email address with SponsorLink's remote servers. There is no option to disable this.

Moq v4.20.2 has removed this functionality.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`moq`	≥ 4.20.0-rc&&< 4.20.2	4.20.2`dotnet add package moq --version 4.20.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for moq, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update moq to 4.20.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6r78-m64m-qwcf 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6r78-m64m-qwcf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6r78-m64m-qwcf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Moq v4.20.0-rc to 4.20.1 include support for [SponsorLink](https://github.com/devlooped/SponsorLink), which runs an obfuscated DLL at build time that scans local `git config` data and shares the user's hashed email address with SponsorLink's remote servers. There is no option to disable this. Moq v4.20.2 has removed this functionality.

O3 Security · Impact-Aware SCA

Is GHSA-6r78-m64m-qwcf in your dependencies?

O3 Security finds GHSA-6r78-m64m-qwcf across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works