● Branch of Go
Go 1.12
Go 1.12 reached end of life on 25 February 2020 and gets no fixes. Move to 1.26.11 or newer.
Data: .
Fix releases of Go 1.12
| Release | Fixes | Signs of exploitation |
|---|---|---|
| 1.12.16 | 2 CVE records | 1 record on CISA's list; 1 record with a public exploit; 1 record with EPSS 0.50 or more |
| 1.12.11 | 1 CVE record | none |
| 1.12.10 | 1 CVE record | none |
| 1.12.8 | 3 CVE records | 2 records with EPSS 0.50 or more |
| 1.12.2 | 1 CVE record | none |
Go 1.12 in dates
| What | When |
|---|---|
| Released | 25 February 2019 |
| Security fixes end | 25 February 2020 |
| Newest release | 1.12.17 (12 February 2020) |
What this page says
Since 25 February 2020, the Go vulnerability database has published advisories that name 230 CVE ids. 8 of them are not placed on a branch. Of the others, 8 give a range of its own for Go 1.12, and 183 give a range with no start that ends in a newer branch; as the advisory states it, that range covers Go 1.12 too.
A record names the branches the project tested, and a branch that has ended is rarely among them. That does not make Go 1.12 safe. Not tested by the project, treat as affected.
A release is the fix of a record when the record's affected range for this branch ends before it. Dates are from the product lifecycle data credited under Sources.
Sources
- Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
- EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)
- Package advisories from the Go vulnerability database (CC BY 4.0). Version ranges are reworded as sentences (source). Licence: CC BY 4.0