Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to instal
Noroxi assessment
Priority: Monitor (action score 38/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.4% (FIRST EPSS); higher than 71.7% 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 (Debian:12) 83.0.4103.83-1; chromium (openSUSE:Leap 15.1) 83.0.4103.97-lp151.2.96.1; chromium-browser (Red Hat:rhel_extras:6) 0:83.0.4103.97-1.el6_10.
Low priority for now. Upgrade to chromium (Debian:12) 83.0.4103.83-1; chromium (openSUSE:Leap 15.1) 83.0.4103.97-lp151.2.96.1; chromium-browser (Red Hat:rhel_extras:6) 0:83.0.4103.97-1.el6_10 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
Insufficient policy enforcement in developer tools in Google Chrome prior to 83.0.4103.61 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted Chrome Extension.
- Published
- May 21, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.4% · 72th percentile
- CWE
- CWE-276
Report tools
Action score
38
Monitor
Low priority for now.
- CVSS
- 38 / 40 · 9.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 | |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| opensuse | backports sle | cpe:2.3:a:opensuse:backports_sle |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
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 fedora31
- fedoraproject fedora32
- google chromebefore 83.0.4103.61
- opensuse backports sle15.0
- opensuse leap15.1
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 83.0.4103.61affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | chromium | before 83.0.4103.83-1 | 83.0.4103.83-1 |
| openSUSE:Leap 15.1 | chromium | before 83.0.4103.97-lp151.2.96.1 | 83.0.4103.97-lp151.2.96.1 |
| Red Hat:rhel_extras:6 | chromium-browser | before 0:83.0.4103.97-1.el6_10 | 0:83.0.4103.97-1.el6_10 |
| Red Hat:rhel_extras:6 | chromium-browser-debuginfo | before 0:83.0.4103.97-1.el6_10 | 0:83.0.4103.97-1.el6_10 |
| SUSE:Package Hub 15 SP1 | chromium | before 83.0.4103.97-bp151.3.85.1 | 83.0.4103.97-bp151.3.85.1 |
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 boKEV95Now
- 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 craftKEV90Now
- 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 sKEV90Now
- CVE-2020-6418Type confusion in V8 in Google Chrome prior to 80.0.3987.122 allowed a remote attacker to potentially exploit heap corruption via a crafted KEV89Now
- CVE-2020-15999Heap buffer overflow in Freetype in Google Chrome prior to 86.0.4240.111 allowed a remote attacker to potentially exploit heap corruption viKEV87Now
- CVE-2022-2294Heap buffer overflow in WebRTC in Google Chrome prior to 103.0.5060.114 allowed a remote attacker to potentially exploit heap corruption viaKEV86Now
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 |
|---|---|---|
| debian:chromium | 83.0.4103.83-1 · Debian:12 | Package registry (OSV) |
| opensuse:chromium | 83.0.4103.97-lp151.2.96.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| red hat:chromium-browser | 0:83.0.4103.97-1.el6_10 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:chromium-browser-debuginfo | 0:83.0.4103.97-1.el6_10 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| suse:chromium | 83.0.4103.97-bp151.3.85.1 · SUSE:Package Hub 15 SP1 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-276 · Incorrect Default PermissionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- lists.opensuse.org/opensuse-security-announce/2020-06/msg00038.html
- chromereleases.googleblog.com/2020/05/stable-channel-update-for-desktop_19.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OQYH5OK7O4BU6E37WWG5SEEHV65BFSGR/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WLFZ5N4EK6I4ZJP5YSKLLVN3ELXEB4XT/
- security.gentoo.org/glsa/202006-02
- security.gentoo.org/glsa/202101-30
- www.debian.org/security/2020/dsa-4714
Vendor advisories and official records. Exploit/PoC links are deliberately left out.