CVE-2020-6425: Insufficient policy enforcement in extensions in Google Chrome prior to 80.0.3987.149 allowed an attacker who convinced a user to install a…
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 68.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: chromium (Alpine:v3.11) 80.0.3987.149-r0; chromium (Debian:10) 80.0.3987.149-1~deb10u1; chromium (Debian:12) 80.0.3987.149-1.
Low priority for now. Upgrade to chromium (Alpine:v3.11) 80.0.3987.149-r0; chromium (Debian:10) 80.0.3987.149-1~deb10u1; chromium (Debian:12) 80.0.3987.149-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Insufficient policy enforcement in extensions in Google Chrome prior to 80.0.3987.149 allowed an attacker who convinced a user to install a malicious extension to bypass site isolation via a crafted Chrome Extension.
- Published
- Mar 23, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 68th percentile
- CWE
- CWE-20
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| chrome | cpe:2.3:a:google:chrome | |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| opensuse | backports | cpe:2.3:o:opensuse:backports |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Chrome). Independent of NVD's CPE analysis and usually ahead of it.
Google Chrome
- unspecified and later · before 80.0.3987.149affected
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- debian debian linux9.0
- fedoraproject fedora30
- fedoraproject fedora31
- fedoraproject fedora32
- google chromebefore 80.0.3987.149
- opensuse backportssle-15
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.11 | chromium | before 80.0.3987.149-r0 | 80.0.3987.149-r0 |
| Debian:10 | chromium | before 80.0.3987.149-1~deb10u1 | 80.0.3987.149-1~deb10u1 |
| Debian:12 | chromium | before 80.0.3987.149-1 | 80.0.3987.149-1 |
| openSUSE:Leap 15.1 | chromium | before 80.0.3987.149-41.1 | 80.0.3987.149-41.1 |
| Red Hat:rhel_extras:6 | chromium-browser | before 0:80.0.3987.149-1.el6_10 | 0:80.0.3987.149-1.el6_10 |
| Red Hat:rhel_extras:6 | chromium-browser-debuginfo | before 0:80.0.3987.149-1.el6_10 | 0:80.0.3987.149-1.el6_10 |
| SUSE:Package Hub 12 SP3 | chromium | before 80.0.3987.149-41.1 | 80.0.3987.149-41.1 |
| SUSE:Package Hub 15 SP1 | chromium | before 80.0.3987.149-bp151.3.63.3 | 80.0.3987.149-bp151.3.63.3 |
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4863Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of…KEV95Now
- CVE-2021-21224Type confusion in V8 in Google Chrome prior to 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox via a…KEV90Now
- CVE-2018-17463Incorrect side effect annotation in V8 in Google Chrome prior to 70.0.3538.64 allowed a remote attacker to execute arbitrary code inside a…KEV90Now
Published before and after this one in the same product
- ← EarlierCVE-2020-6422Mar 23, 2020 · Use after free in WebGL in Google Chrome prior to 80.0.3987.149 allowed a remote attacker to potentially exploit heap corruption via a…36Monitor
- ← EarlierCVE-2020-6424Mar 23, 2020 · Use after free in media in Google Chrome prior to 80.0.3987.149 allowed a remote attacker to potentially exploit heap corruption via a…36Monitor
- Later →CVE-2020-6426Mar 23, 2020 · Inappropriate implementation in V8 in Google Chrome prior to 80.0.3987.149 allowed a remote attacker to potentially exploit heap corruption…27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:chromium | 80.0.3987.149-r0 · Alpine:v3.11 | Package registry (OSV) |
| debian:chromium | 80.0.3987.149-1 · Debian:12 | Package registry (OSV) |
| opensuse:chromium | 80.0.3987.149-41.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| red hat:chromium-browser | 0:80.0.3987.149-1.el6_10 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:chromium-browser-debuginfo | 0:80.0.3987.149-1.el6_10 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| suse:chromium | 80.0.3987.149-41.1 · SUSE:Package Hub 12 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- chromereleases.googleblog.com/2020/03/stable-channel-update-for-desktop_18.html
- crbug.com/1031670
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/2DDNOAGIX5D77TTHT6YPMVJ5WTXTCQEI/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6IOHSO6BUKC6I66J5PZOMAGFVJ66ZS57/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JWANFIR3PYAL5RJQ4AO3ZS2DYMSF2ZGZ/
- security.gentoo.org/glsa/202003-53
- www.debian.org/security/2020/dsa-4645
Vendor advisories and official records. Exploit/PoC links are deliberately left out.