How severe is GHSA-879p-8gw4-mcpw?

GHSA-879p-8gw4-mcpw has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-879p-8gw4-mcpw?

GHSA-879p-8gw4-mcpw affects the following packages: fgr (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-879p-8gw4-mcpw?

The records we use list no patched version of fgr for GHSA-879p-8gw4-mcpw. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-879p-8gw4-mcpw in my PyPI dependencies?

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

How do I mitigate GHSA-879p-8gw4-mcpw 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-879p-8gw4-mcpw actively exploited in the wild?

No public exploit code has been indexed for GHSA-879p-8gw4-mcpw 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-879p-8gw4-mcpw published, and has it been updated?

GHSA-879p-8gw4-mcpw was published on March 15, 2024 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

LOW severity

fgr Vulnerable to Insecure Default Variable InitializationGHSA-879p-8gw4-mcpw

LOW

GHSA-879p-8gw4-mcpw is a low-severity (CVSS 3.7) vulnerability in fgr. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published

Mar 15, 2024

Updated

Dec 4, 2024

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐍fgr

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

Description

Impact

Any users whom would not desire a traceback to be included in their logs whenever an error is raised in their code will be affected.

If users have inadvertently created a scenario in their code that could cause a traceback to include sensitive information and a malicious entity gained access to their log stream, this could create an issue.

Patches

None yet... users will need to upgrade to 0.4.*

Workarounds

No particularly reasonable ones at present.

References

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`fgr`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fgr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of fgr for GHSA-879p-8gw4-mcpw. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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

### Impact Any users whom would not desire a traceback to be included in their logs whenever an error is raised in their code will be affected. If users have inadvertently created a scenario in their code that could cause a traceback to include sensitive information _and_ a malicious entity gained access to their log stream, this could create an issue. ### Patches None yet... users will need to upgrade to `0.4.*` ### Workarounds No particularly reasonable ones at present. ### References * https://cwe.mitre.org/data/definitions/453.html * https://www.invicti.com/web-vulnerability-scanner/vu

O3 Security · Impact-Aware SCA

Is GHSA-879p-8gw4-mcpw in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works