CVE-2020-8927
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 · uneditedA buffer overflow exists in the Brotli library versions prior to 1.0.8 where an attacker controlling the input length of a "one-shot" decompression request to a script can trigger a crash, which happens when copying over chunks of data larger than 2 GiB. It is recommended to update your Brotli library to 1.0.8 or later. If one cannot update, we recommend to use the "streaming" API as opposed to the "one-shot" API, and impose chunk size limits.
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 confidenceBuffer overflow in Brotli library versions prior to 1.0.8 where an attacker controlling the input length of a 'one-shot' decompression request can trigger a crash by providing data that causes chunks larger than 2 GiB to be copied during decompression.
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= 9.0= 10.0= 31= 32= 33= 34= 35= 36= 16.04= 18.04= 20.04< 1.0.8= 15.2>= 5.0, <= 5.0.14>= 3.1, <= 3.1.22>= 7.0, < 7.0.9>= 7.1, < 7.1.6>= 7.2, < 7.2.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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 installed Brotli library versionRun 'brotli --version' or check package manager: 'dpkg -l | grep brotli' (Debian/Ubuntu), 'rpm -qa | grep brotli' (Fedora), or inspect the shared library file for version infoAffected if Version is lower than 1.0.8 (e.g., 1.0.7, 1.0.6, etc.)
-
Identify PowerShell versionRun 'pwsh --version' or 'powershell -Command $PSVersionTable.PSVersion'Affected if Version is 7.0.x below 7.0.9, 7.1.x below 7.1.6, or 7.2.x below 7.2.2
-
Identify .NET runtime versionRun 'dotnet --list-runtimes' to see installed .NET Core/5+ runtimes, or check registry on Windows for installed versionsAffected if .NET 5.0.x at or below 5.0.14, or .NET Core 3.1.x at or below 3.1.22 is installed
-
Verify one-shot decompression API usageSearch codebase for calls to BrotliDecoder.Decode or similar one-shot decompression functions (non-streaming) that accept user-supplied input length parametersAffected if Code uses the one-shot (non-streaming) decompression API where an attacker can control the input length
-
Check for large input handlingReview if decompression logic processes input that could result in chunks exceeding 2 GiB during decompressionAffected if Application decompresses untrusted Brotli-compressed data without chunk size limits
You are affected if you have a vulnerable Brotli library version (<1.0.8), vulnerable .NET/PowerShell version, AND your code uses the one-shot decompression API with attacker-controlled input that could produce decompressed chunks larger than 2 GiB.
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 data1.0.87.0.97.1.6
Update Brotli library to version 1.0.8 or later; alternatively, refactor code to use the streaming API instead of one-shot API with enforced chunk size limits.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8927 — 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 sources- lists.opensuse.org
- github.com
- lists.debian.org
- usn.ubuntu.com
- www.debian.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-8927 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