GHSA-r2r8-36pq-27cm json
nzo/url-encryptor-bundle Insecure default secret key and IV allowing anyone to decrypt values
published 2y ago modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist nzo/url-encryptor-bundle 4.3.2, 5.0.1
Is GHSA-r2r8-36pq-27cm in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | nzo/url-encryptor-bundle | >=5.0.0, <5.0.1 >=4.0.0, <4.3.2 |
5.0.1 4.3.2 |
References
-
github.com
/nayzo/NzoUrlEncryptorBundle/commit/ba3af1a9bcf3bedcc0ed5948979f482e2134da1a
web
-
github.com
/nayzo/NzoUrlEncryptorBundle/commit/bd8232501c12c9df1bc45b1970870ef665218581
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/nzo/url-encryptor-bundle/2020-05-03.yaml
web
-
github.com
/nayzo/NzoUrlEncryptorBundle
package
Sources
- GitHub Advisory GHSA-r2r8-36pq-27cm
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.