CVE-2020-9690 json
Magento observable timing discrepancy vulnerability
published 6y ago modified 2mo ago also BIT-magento-2020-9690 , EUVD-2022-5786 , GHSA-xgp9-j48h-jjf9
- cvss
- 4.2
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
Magento versions 2.3.5-p1 and earlier, and 2.3.5-p1 and earlier have an observable timing discrepancy vulnerability. Successful exploitation could lead to signature verification bypass.
Patch / fix
- packagist magento/community-edition 2.3.5-p2
- bitnami magento 2.3.5
- magento magento 2.3.5
Is CVE-2020-9690 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 FencerExploit prediction
1.85% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 4.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 4.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:P/A:N |
| OSV | 3.1 | 4.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | magento/community-edition | <2.3.5-p2 |
2.3.5-p2 |
| bitnami | magento | <2.3.5 |
2.3.5 |
Affected products
- Adobe Magento
Classification
- Weakness
-
- CWE-203 Observable Discrepancy
References
-
helpx.adobe.com
/security/products/magento/apsb20-47.html
web, patch, vendor-advisory, advisory
-
github.com
/magento/magento2/commit/9436781734e47c83e96977fa770d255217680d5e
web
-
nvd.nist.gov
/vuln/detail/CVE-2020-9690
advisory, web
-
github.com
/magento/magento2
package
Sources
- CVE List CVE-2020-9690
- GitHub Advisory GHSA-xgp9-j48h-jjf9
- NVD CVE-2020-9690
- OSV BIT-magento-2020-9690
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.