GHSA-gmx7-gr5q-85w5 — magic-crypt
GHSA-gmx7-gr5q-85w5 is a security vulnerability in magic-crypt. No vendor fix is recorded yet; mitigation options are listed below.
magic-crypt uses insecure cryptographic algorithms
Real-World Exposure
magic-cryptReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
This crate uses a number of cryptographic algorithms that are no longer considered secure and it uses them in ways that do not guarantee the integrity of the encrypted data.
MagicCrypt64 uses the insecure DES block cipher in CBC mode without authentication. This allows for practical brute force and padding oracle attacks and does not protect the integrity of the encrypted data. Key and IV are generated from user input using CRC64, which is not at all a key derivation function.
MagicCrypt64, MagicCrypt128, MagicCrypt192, and MagicCrypt256 are all vulnerable to padding-oracle attacks. None of them protect the integrity of the ciphertext. Furthermore, none use password-based key derivation functions, even though the key is intended to be generated from a password.
Each of the implementations are unsound in that they use uninitialized memory without MaybeUninit or equivalent structures.
For more information, visit the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | magic-crypt | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magic-crypt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of magic-crypt has shipped for GHSA-gmx7-gr5q-85w5 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gmx7-gr5q-85w5 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-gmx7-gr5q-85w5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-gmx7-gr5q-85w5 in your dependencies?
O3 Security finds GHSA-gmx7-gr5q-85w5 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.