GHSA-r2r8-36pq-27cm — nzo/url-encryptor-bundle
Fix: nayzo/NzoUrlEncryptorBundle@ba3af1aGHSA-r2r8-36pq-27cm is a security vulnerability in nzo/url-encryptor-bundle. A fix is available for nzo/url-encryptor-bundle — see the affected versions and patch details below.
nzo/url-encryptor-bundle Insecure default secret key and IV allowing anyone to decrypt values
Real-World Exposure
nzo/url-encryptor-bundle🐘nzo/url-encryptor-bundleReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Versions of nzo/url-encryptor-bundle prior to 5.0.1 and 4.3.2 are affected by a security vulnerability related to the lack of mandatory key and IV requirements. By default, the bundle uses the aes-256-ctr algorithm, which is susceptible to malleability attacks, potentially leading to Insecure Direct Object Reference (IDOR) vulnerabilities. Additionally, the reuse of keys enables users to decrypt and modify encrypted data if they can guess the plaintext of one ciphertext.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | nzo/url-encryptor-bundle | ≥ 5.0.0&&< 5.0.1 | 5.0.1composer require nzo/url-encryptor-bundle:^5.0.1 |
| 🐘Packagist | nzo/url-encryptor-bundle | ≥ 4.0.0&&< 4.3.2 | 4.3.2composer require nzo/url-encryptor-bundle:^4.3.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nzo/url-encryptor-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nzo/url-encryptor-bundle to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r2r8-36pq-27cm 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-r2r8-36pq-27cm can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r2r8-36pq-27cm. 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-r2r8-36pq-27cm in your dependencies?
O3 Security finds GHSA-r2r8-36pq-27cm across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.