Chainbrave-browser
brave-browser: incomplete fixes (2021)
3 CVEs over 2 generations, 23 Feb 2021 to 27 Dec 2021.
Family tree
Left to right by publication date.Oldest first. Select a CVE to open it.- CVE-2021-2132323 Feb 2021 First in the chain
- CVE-2021-2291612 Jul 2021 No direct link to an earlier CVE
- CVE-2021-4588427 Dec 2021 incomplete fix for CVE-2021-21323incomplete fix for CVE-2021-22916
Exploited in the wild (CISA KEV) Not in KEV Priority score (0 to 100) High confidence Medium Low Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
CVEs in this family
Table view of the tree| CVE | Published | Title | Linked from | Priority |
|---|---|---|---|---|
| CVE-2021-21323 | 23 Feb 2021 | Regression in DNS leakage from Tor windows | First in chain | 19.6 |
| CVE-2021-22916 | 12 Jul 2021 | In Brave Desktop between versions 1.17 and 1.26.60, when adblocking is enabled and a proxy browser extension is… | First in chain | 17.5 |
| CVE-2021-45884 | 27 Dec 2021 | In Brave Desktop 1.17 through 1.33 before 1.33.106, when CNAME-based adblocking and a proxying extension with a SOCKS… | CVE-2021-21323 · incomplete fix · High | 17.6 |