How severe is GHSA-5grr-72f9-678v?

No CVSS score has been assigned to GHSA-5grr-72f9-678v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5grr-72f9-678v?

GHSA-5grr-72f9-678v affects the following packages: cipherbcrypt (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-5grr-72f9-678v?

The records we use list no patched version of cipherbcrypt for GHSA-5grr-72f9-678v. 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-5grr-72f9-678v in my PyPI dependencies?

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

How do I mitigate GHSA-5grr-72f9-678v 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-5grr-72f9-678v actively exploited in the wild?

No public exploit code has been indexed for GHSA-5grr-72f9-678v 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-5grr-72f9-678v published, and has it been updated?

GHSA-5grr-72f9-678v was published on July 12, 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

Malware package cipherbcryptGHSA-5grr-72f9-678v

Fix: pypa/advisory-database@f8df7b7

GHSA-5grr-72f9-678v is a security vulnerability in cipherbcrypt. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Published

Jul 12, 2024

Updated

Jul 12, 2024

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Jul 12, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍cipherbcrypt

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

Malicious package. Exfiltrated secrets to a target server.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`cipherbcrypt`	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 cipherbcrypt, 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 cipherbcrypt for GHSA-5grr-72f9-678v. 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

Malicious package. Exfiltrated secrets to a target server.

O3 Security · Impact-Aware SCA

Is GHSA-5grr-72f9-678v in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works