CVE-2020-9588
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMagento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have an observable timing discrepancy vulnerability. Successful exploitation could lead to signature verification bypass.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMagento contains an observable timing discrepancy vulnerability in its signature verification process. The system takes measurably different amounts of time to process requests depending on whether a signature is valid or certain conditions are met. Attackers can exploit this timing difference to deduce correct signature values through repeated attempts, ultimately bypassing signature verification.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.9.4.4<= 1.14.4.4>= 2.2.0, <= 2.2.11>= 2.3.0, <= 2.3.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your Magento installation versionFor Magento 1.x: Check the version file in the root directory or app/etc/local.xml. For Magento 2.x: Run 'bin/magento --version' from the installation root or check composer.jsonAffected if The installed version is not clearly visible or cannot be determined from standard version files
-
Compare Magento 1.x version against affected rangesIf running Magento 1.x, check if the version is <= 1.9.4.4 or <= 1.14.4.4Affected if The installed Magento 1.x version falls at or below 1.9.4.4, or at or below 1.14.4.4
-
Compare Magento 2.2.x version against affected rangesIf running Magento 2.2.x, check if the version is >= 2.2.0 and <= 2.2.11Affected if The installed Magento 2.2.x version is between 2.2.0 and 2.2.11 inclusive
-
Compare Magento 2.3.x version against affected rangesIf running Magento 2.3.x, check if the version is >= 2.3.0 and <= 2.3.4Affected if The installed Magento 2.3.x version is between 2.3.0 and 2.3.4 inclusive
-
Verify signature verification is in useDetermine if the Magento installation uses signature verification for any extensions, modules, or API integrations. Check configuration files in app/etc or the admin panel under Stores > ConfigurationAffected if The installation uses signature verification and the version falls within any of the affected ranges listed above
Your environment is affected if the installed Magento version falls within any of these ranges: 1.9.4.4 or lower, 1.14.4.4 or lower, 2.2.0 to 2.2.11, or 2.3.0 to 2.3.4, and signature verification is actively used.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor patch for CVE-2020-9588 which implements constant-time signature comparison to eliminate timing side channels. Ensure all Magento installations are updated to the patched versions.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9588 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-9588 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data