# Unauthenticated crypto and weak IV in Magento\Framework\Encryption

Advisory record · `GHSA-h7qw-mxrm-c6h2`

- **Identifiers:** `GHSA-h7qw-mxrm-c6h2` · `CVE-2016-6485` · `PKSA-3wsp-2gmh-pcsq` · `PKSA-4kzn-6ry6-q5bh` · `PKSA-whwg-zcv6-qs4x`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-327](https://cwe.mitre.org/data/definitions/327.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 20 Nov 2019
- **Updated:** 10 Feb 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Nov 2019, 01:33 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `magento/community-edition` (Packagist): affected `>=2.0, <2.2.6`; fixed in `2.2.6`
- `magento/project-community-edition` (Packagist): affected `>=2.0, <=2.0.2`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Magento Community Edition (magento/community-edition) versions from 2.0 before 2.2.6, and magento/project-community-edition versions up to 2.0.2, contain a weak initialization vector in the encryption framework. The constructor of the Crypt class generates the IV with PHP's rand function, which a remote attacker can exploit by guessing the value to defeat the cryptographic protection. Upgrade magento/community-edition to 2.2.6. No fixed version is listed for magento/project-community-edition.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0085, the 58th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:28 UTC: First seen by agentprime
- 31 Oct 2026, 14:28 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-h7qw-mxrm-c6h2)

## Sources

- [GitHub Advisory Database: GHSA-h7qw-mxrm-c6h2](https://github.com/advisories/GHSA-h7qw-mxrm-c6h2)
- [OSV: GHSA-h7qw-mxrm-c6h2](https://osv.dev/vulnerability/GHSA-h7qw-mxrm-c6h2)
- <https://nvd.nist.gov/vuln/detail/CVE-2016-6485>
- <https://github.com/magento/magento2/pull/15017>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/magento/product-community-edition/CVE-2016-6485.yaml>
- <http://www.openwall.com/lists/oss-security/2016/07/19/3>
- <http://www.openwall.com/lists/oss-security/2016/07/27/14>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-h7qw-mxrm-c6h2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h7qw-mxrm-c6h2/>. Everything for agents: <https://agentprime.io/llms.txt>.
