| 1 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| 2 |
Gentoo Linux Security Advisory GLSA 202208-25 |
| 3 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| 4 |
https://security.gentoo.org/ |
| 5 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| 6 |
|
| 7 |
Severity: High |
| 8 |
Title: Chromium, Google Chrome, Microsoft Edge, QtWebEngine: Multiple Vulnerabilities |
| 9 |
Date: August 14, 2022 |
| 10 |
Bugs: #828519, #834477, #835397, #836011, #836381, #836777, #838049, #838433, #841371, #843728, #847370, #851003, #853643, #773040, #787950, #800181, #810781, #815397, #829161, #835761, #836830, #847613, #853229, #837497, #838682, #843035, #848864, #851009, #854372 |
| 11 |
ID: 202208-25 |
| 12 |
|
| 13 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| 14 |
|
| 15 |
Synopsis |
| 16 |
======== |
| 17 |
|
| 18 |
Multiple vulnerabilities have been found in Chromium and its |
| 19 |
derivatives, the worst of which could result in remote code execution. |
| 20 |
|
| 21 |
Background |
| 22 |
========== |
| 23 |
|
| 24 |
Chromium is an open-source browser project that aims to build a safer, |
| 25 |
faster, and more stable way for all users to experience the web. |
| 26 |
|
| 27 |
Google Chrome is one fast, simple, and secure browser for all your |
| 28 |
devices. |
| 29 |
|
| 30 |
Microsoft Edge is a browser that combines a minimal design with |
| 31 |
sophisticated technology to make the web faster, safer, and easier. |
| 32 |
|
| 33 |
Affected packages |
| 34 |
================= |
| 35 |
|
| 36 |
------------------------------------------------------------------- |
| 37 |
Package / Vulnerable / Unaffected |
| 38 |
------------------------------------------------------------------- |
| 39 |
1 dev-qt/qtwebengine < 5.15.5_p20220618>= 5.15.5_p20220618 |
| 40 |
2 www-client/chromium < 103.0.5060.53 >= 103.0.5060.53 |
| 41 |
3 www-client/google-chrome < 103.0.5060.53 >= 103.0.5060.53 |
| 42 |
4 www-client/microsoft-edge < 101.0.1210.47 >= 101.0.1210.47 |
| 43 |
|
| 44 |
Description |
| 45 |
=========== |
| 46 |
|
| 47 |
Multiple vulnerabilities have been discovered in Chromium and its |
| 48 |
derivatives. Please review the CVE identifiers referenced below for |
| 49 |
details. |
| 50 |
|
| 51 |
Impact |
| 52 |
====== |
| 53 |
|
| 54 |
Please review the referenced CVE identifiers for details. |
| 55 |
|
| 56 |
Workaround |
| 57 |
========== |
| 58 |
|
| 59 |
There is no known workaround at this time. |
| 60 |
|
| 61 |
Resolution |
| 62 |
========== |
| 63 |
|
| 64 |
All Chromium users should upgrade to the latest version: |
| 65 |
|
| 66 |
# emerge --sync |
| 67 |
# emerge --ask --oneshot --verbose ">=www-client/chromium-103.0.5060.53" |
| 68 |
|
| 69 |
All Chromium binary users should upgrade to the latest version: |
| 70 |
|
| 71 |
# emerge --sync |
| 72 |
# emerge --ask --oneshot --verbose ">=www-client/chromium-bin-103.0.5060.53" |
| 73 |
|
| 74 |
All Google Chrome users should upgrade to the latest version: |
| 75 |
|
| 76 |
# emerge --sync |
| 77 |
# emerge --ask --oneshot --verbose ">=www-client/google-chrome-103.0.5060.53" |
| 78 |
|
| 79 |
All Microsoft Edge users should upgrade to the latest version: |
| 80 |
|
| 81 |
# emerge --sync |
| 82 |
# emerge --ask --oneshot --verbose ">=www-client/chromium-103.0.5060.53" |
| 83 |
|
| 84 |
All QtWebEngine users should upgrade to the latest version: |
| 85 |
|
| 86 |
# emerge --sync |
| 87 |
# emerge --ask --oneshot --verbose ">=dev-qt/qtwebengine-5.15.5_p20220618" |
| 88 |
|
| 89 |
References |
| 90 |
========== |
| 91 |
|
| 92 |
[ 1 ] CVE-2021-4052 |
| 93 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4052 |
| 94 |
[ 2 ] CVE-2021-4053 |
| 95 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4053 |
| 96 |
[ 3 ] CVE-2021-4054 |
| 97 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4054 |
| 98 |
[ 4 ] CVE-2021-4055 |
| 99 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4055 |
| 100 |
[ 5 ] CVE-2021-4056 |
| 101 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4056 |
| 102 |
[ 6 ] CVE-2021-4057 |
| 103 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4057 |
| 104 |
[ 7 ] CVE-2021-4058 |
| 105 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4058 |
| 106 |
[ 8 ] CVE-2021-4059 |
| 107 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4059 |
| 108 |
[ 9 ] CVE-2021-4061 |
| 109 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4061 |
| 110 |
[ 10 ] CVE-2021-4062 |
| 111 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4062 |
| 112 |
[ 11 ] CVE-2021-4063 |
| 113 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4063 |
| 114 |
[ 12 ] CVE-2021-4064 |
| 115 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4064 |
| 116 |
[ 13 ] CVE-2021-4065 |
| 117 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4065 |
| 118 |
[ 14 ] CVE-2021-4066 |
| 119 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4066 |
| 120 |
[ 15 ] CVE-2021-4067 |
| 121 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4067 |
| 122 |
[ 16 ] CVE-2021-4068 |
| 123 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4068 |
| 124 |
[ 17 ] CVE-2021-4078 |
| 125 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4078 |
| 126 |
[ 18 ] CVE-2021-4079 |
| 127 |
https://nvd.nist.gov/vuln/detail/CVE-2021-4079 |
| 128 |
[ 19 ] CVE-2021-30551 |
| 129 |
https://nvd.nist.gov/vuln/detail/CVE-2021-30551 |
| 130 |
[ 20 ] CVE-2022-0789 |
| 131 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0789 |
| 132 |
[ 21 ] CVE-2022-0790 |
| 133 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0790 |
| 134 |
[ 22 ] CVE-2022-0791 |
| 135 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0791 |
| 136 |
[ 23 ] CVE-2022-0792 |
| 137 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0792 |
| 138 |
[ 24 ] CVE-2022-0793 |
| 139 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0793 |
| 140 |
[ 25 ] CVE-2022-0794 |
| 141 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0794 |
| 142 |
[ 26 ] CVE-2022-0795 |
| 143 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0795 |
| 144 |
[ 27 ] CVE-2022-0796 |
| 145 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0796 |
| 146 |
[ 28 ] CVE-2022-0797 |
| 147 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0797 |
| 148 |
[ 29 ] CVE-2022-0798 |
| 149 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0798 |
| 150 |
[ 30 ] CVE-2022-0799 |
| 151 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0799 |
| 152 |
[ 31 ] CVE-2022-0800 |
| 153 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0800 |
| 154 |
[ 32 ] CVE-2022-0801 |
| 155 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0801 |
| 156 |
[ 33 ] CVE-2022-0802 |
| 157 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0802 |
| 158 |
[ 34 ] CVE-2022-0803 |
| 159 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0803 |
| 160 |
[ 35 ] CVE-2022-0804 |
| 161 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0804 |
| 162 |
[ 36 ] CVE-2022-0805 |
| 163 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0805 |
| 164 |
[ 37 ] CVE-2022-0806 |
| 165 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0806 |
| 166 |
[ 38 ] CVE-2022-0807 |
| 167 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0807 |
| 168 |
[ 39 ] CVE-2022-0808 |
| 169 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0808 |
| 170 |
[ 40 ] CVE-2022-0809 |
| 171 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0809 |
| 172 |
[ 41 ] CVE-2022-0971 |
| 173 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0971 |
| 174 |
[ 42 ] CVE-2022-0972 |
| 175 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0972 |
| 176 |
[ 43 ] CVE-2022-0973 |
| 177 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0973 |
| 178 |
[ 44 ] CVE-2022-0974 |
| 179 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0974 |
| 180 |
[ 45 ] CVE-2022-0975 |
| 181 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0975 |
| 182 |
[ 46 ] CVE-2022-0976 |
| 183 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0976 |
| 184 |
[ 47 ] CVE-2022-0977 |
| 185 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0977 |
| 186 |
[ 48 ] CVE-2022-0978 |
| 187 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0978 |
| 188 |
[ 49 ] CVE-2022-0979 |
| 189 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0979 |
| 190 |
[ 50 ] CVE-2022-0980 |
| 191 |
https://nvd.nist.gov/vuln/detail/CVE-2022-0980 |
| 192 |
[ 51 ] CVE-2022-1096 |
| 193 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1096 |
| 194 |
[ 52 ] CVE-2022-1125 |
| 195 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1125 |
| 196 |
[ 53 ] CVE-2022-1127 |
| 197 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1127 |
| 198 |
[ 54 ] CVE-2022-1128 |
| 199 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1128 |
| 200 |
[ 55 ] CVE-2022-1129 |
| 201 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1129 |
| 202 |
[ 56 ] CVE-2022-1130 |
| 203 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1130 |
| 204 |
[ 57 ] CVE-2022-1131 |
| 205 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1131 |
| 206 |
[ 58 ] CVE-2022-1132 |
| 207 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1132 |
| 208 |
[ 59 ] CVE-2022-1133 |
| 209 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1133 |
| 210 |
[ 60 ] CVE-2022-1134 |
| 211 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1134 |
| 212 |
[ 61 ] CVE-2022-1135 |
| 213 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1135 |
| 214 |
[ 62 ] CVE-2022-1136 |
| 215 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1136 |
| 216 |
[ 63 ] CVE-2022-1137 |
| 217 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1137 |
| 218 |
[ 64 ] CVE-2022-1138 |
| 219 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1138 |
| 220 |
[ 65 ] CVE-2022-1139 |
| 221 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1139 |
| 222 |
[ 66 ] CVE-2022-1141 |
| 223 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1141 |
| 224 |
[ 67 ] CVE-2022-1142 |
| 225 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1142 |
| 226 |
[ 68 ] CVE-2022-1143 |
| 227 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1143 |
| 228 |
[ 69 ] CVE-2022-1144 |
| 229 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1144 |
| 230 |
[ 70 ] CVE-2022-1145 |
| 231 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1145 |
| 232 |
[ 71 ] CVE-2022-1146 |
| 233 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1146 |
| 234 |
[ 72 ] CVE-2022-1232 |
| 235 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1232 |
| 236 |
[ 73 ] CVE-2022-1305 |
| 237 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1305 |
| 238 |
[ 74 ] CVE-2022-1306 |
| 239 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1306 |
| 240 |
[ 75 ] CVE-2022-1307 |
| 241 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1307 |
| 242 |
[ 76 ] CVE-2022-1308 |
| 243 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1308 |
| 244 |
[ 77 ] CVE-2022-1309 |
| 245 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1309 |
| 246 |
[ 78 ] CVE-2022-1310 |
| 247 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1310 |
| 248 |
[ 79 ] CVE-2022-1311 |
| 249 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1311 |
| 250 |
[ 80 ] CVE-2022-1312 |
| 251 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1312 |
| 252 |
[ 81 ] CVE-2022-1313 |
| 253 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1313 |
| 254 |
[ 82 ] CVE-2022-1314 |
| 255 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1314 |
| 256 |
[ 83 ] CVE-2022-1364 |
| 257 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1364 |
| 258 |
[ 84 ] CVE-2022-1477 |
| 259 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1477 |
| 260 |
[ 85 ] CVE-2022-1478 |
| 261 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1478 |
| 262 |
[ 86 ] CVE-2022-1479 |
| 263 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1479 |
| 264 |
[ 87 ] CVE-2022-1480 |
| 265 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1480 |
| 266 |
[ 88 ] CVE-2022-1481 |
| 267 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1481 |
| 268 |
[ 89 ] CVE-2022-1482 |
| 269 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1482 |
| 270 |
[ 90 ] CVE-2022-1483 |
| 271 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1483 |
| 272 |
[ 91 ] CVE-2022-1484 |
| 273 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1484 |
| 274 |
[ 92 ] CVE-2022-1485 |
| 275 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1485 |
| 276 |
[ 93 ] CVE-2022-1486 |
| 277 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1486 |
| 278 |
[ 94 ] CVE-2022-1487 |
| 279 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1487 |
| 280 |
[ 95 ] CVE-2022-1488 |
| 281 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1488 |
| 282 |
[ 96 ] CVE-2022-1489 |
| 283 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1489 |
| 284 |
[ 97 ] CVE-2022-1490 |
| 285 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1490 |
| 286 |
[ 98 ] CVE-2022-1491 |
| 287 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1491 |
| 288 |
[ 99 ] CVE-2022-1492 |
| 289 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1492 |
| 290 |
[ 100 ] CVE-2022-1493 |
| 291 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1493 |
| 292 |
[ 101 ] CVE-2022-1494 |
| 293 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1494 |
| 294 |
[ 102 ] CVE-2022-1495 |
| 295 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1495 |
| 296 |
[ 103 ] CVE-2022-1496 |
| 297 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1496 |
| 298 |
[ 104 ] CVE-2022-1497 |
| 299 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1497 |
| 300 |
[ 105 ] CVE-2022-1498 |
| 301 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1498 |
| 302 |
[ 106 ] CVE-2022-1499 |
| 303 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1499 |
| 304 |
[ 107 ] CVE-2022-1500 |
| 305 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1500 |
| 306 |
[ 108 ] CVE-2022-1501 |
| 307 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1501 |
| 308 |
[ 109 ] CVE-2022-1633 |
| 309 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1633 |
| 310 |
[ 110 ] CVE-2022-1634 |
| 311 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1634 |
| 312 |
[ 111 ] CVE-2022-1635 |
| 313 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1635 |
| 314 |
[ 112 ] CVE-2022-1636 |
| 315 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1636 |
| 316 |
[ 113 ] CVE-2022-1637 |
| 317 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1637 |
| 318 |
[ 114 ] CVE-2022-1639 |
| 319 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1639 |
| 320 |
[ 115 ] CVE-2022-1640 |
| 321 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1640 |
| 322 |
[ 116 ] CVE-2022-1641 |
| 323 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1641 |
| 324 |
[ 117 ] CVE-2022-1853 |
| 325 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1853 |
| 326 |
[ 118 ] CVE-2022-1854 |
| 327 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1854 |
| 328 |
[ 119 ] CVE-2022-1855 |
| 329 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1855 |
| 330 |
[ 120 ] CVE-2022-1856 |
| 331 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1856 |
| 332 |
[ 121 ] CVE-2022-1857 |
| 333 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1857 |
| 334 |
[ 122 ] CVE-2022-1858 |
| 335 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1858 |
| 336 |
[ 123 ] CVE-2022-1859 |
| 337 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1859 |
| 338 |
[ 124 ] CVE-2022-1860 |
| 339 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1860 |
| 340 |
[ 125 ] CVE-2022-1861 |
| 341 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1861 |
| 342 |
[ 126 ] CVE-2022-1862 |
| 343 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1862 |
| 344 |
[ 127 ] CVE-2022-1863 |
| 345 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1863 |
| 346 |
[ 128 ] CVE-2022-1864 |
| 347 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1864 |
| 348 |
[ 129 ] CVE-2022-1865 |
| 349 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1865 |
| 350 |
[ 130 ] CVE-2022-1866 |
| 351 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1866 |
| 352 |
[ 131 ] CVE-2022-1867 |
| 353 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1867 |
| 354 |
[ 132 ] CVE-2022-1868 |
| 355 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1868 |
| 356 |
[ 133 ] CVE-2022-1869 |
| 357 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1869 |
| 358 |
[ 134 ] CVE-2022-1870 |
| 359 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1870 |
| 360 |
[ 135 ] CVE-2022-1871 |
| 361 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1871 |
| 362 |
[ 136 ] CVE-2022-1872 |
| 363 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1872 |
| 364 |
[ 137 ] CVE-2022-1873 |
| 365 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1873 |
| 366 |
[ 138 ] CVE-2022-1874 |
| 367 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1874 |
| 368 |
[ 139 ] CVE-2022-1875 |
| 369 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1875 |
| 370 |
[ 140 ] CVE-2022-1876 |
| 371 |
https://nvd.nist.gov/vuln/detail/CVE-2022-1876 |
| 372 |
[ 141 ] CVE-2022-2007 |
| 373 |
https://nvd.nist.gov/vuln/detail/CVE-2022-2007 |
| 374 |
[ 142 ] CVE-2022-2010 |
| 375 |
https://nvd.nist.gov/vuln/detail/CVE-2022-2010 |
| 376 |
[ 143 ] CVE-2022-2011 |
| 377 |
https://nvd.nist.gov/vuln/detail/CVE-2022-2011 |
| 378 |
[ 144 ] CVE-2022-2156 |
| 379 |
https://nvd.nist.gov/vuln/detail/CVE-2022-2156 |
| 380 |
[ 145 ] CVE-2022-2157 |
| 381 |
https://nvd.nist.gov/vuln/detail/CVE-2022-2157 |
| 382 |
[ 146 ] CVE-2022-2158 |
| 383 |
https://nvd.nist.gov/vuln/detail/CVE-2022-2158 |
| 384 |
[ 147 ] CVE-2022-2160 |
| 385 |
https://nvd.nist.gov/vuln/detail/CVE-2022-2160 |
| 386 |
[ 148 ] CVE-2022-2161 |
| 387 |
https://nvd.nist.gov/vuln/detail/CVE-2022-2161 |
| 388 |
[ 149 ] CVE-2022-2162 |
| 389 |
https://nvd.nist.gov/vuln/detail/CVE-2022-2162 |
| 390 |
[ 150 ] CVE-2022-2163 |
| 391 |
https://nvd.nist.gov/vuln/detail/CVE-2022-2163 |
| 392 |
[ 151 ] CVE-2022-2164 |
| 393 |
https://nvd.nist.gov/vuln/detail/CVE-2022-2164 |
| 394 |
[ 152 ] CVE-2022-2165 |
| 395 |
https://nvd.nist.gov/vuln/detail/CVE-2022-2165 |
| 396 |
[ 153 ] CVE-2022-22021 |
| 397 |
https://nvd.nist.gov/vuln/detail/CVE-2022-22021 |
| 398 |
[ 154 ] CVE-2022-24475 |
| 399 |
https://nvd.nist.gov/vuln/detail/CVE-2022-24475 |
| 400 |
[ 155 ] CVE-2022-24523 |
| 401 |
https://nvd.nist.gov/vuln/detail/CVE-2022-24523 |
| 402 |
[ 156 ] CVE-2022-26891 |
| 403 |
https://nvd.nist.gov/vuln/detail/CVE-2022-26891 |
| 404 |
[ 157 ] CVE-2022-26894 |
| 405 |
https://nvd.nist.gov/vuln/detail/CVE-2022-26894 |
| 406 |
[ 158 ] CVE-2022-26895 |
| 407 |
https://nvd.nist.gov/vuln/detail/CVE-2022-26895 |
| 408 |
[ 159 ] CVE-2022-26900 |
| 409 |
https://nvd.nist.gov/vuln/detail/CVE-2022-26900 |
| 410 |
[ 160 ] CVE-2022-26905 |
| 411 |
https://nvd.nist.gov/vuln/detail/CVE-2022-26905 |
| 412 |
[ 161 ] CVE-2022-26908 |
| 413 |
https://nvd.nist.gov/vuln/detail/CVE-2022-26908 |
| 414 |
[ 162 ] CVE-2022-26909 |
| 415 |
https://nvd.nist.gov/vuln/detail/CVE-2022-26909 |
| 416 |
[ 163 ] CVE-2022-26912 |
| 417 |
https://nvd.nist.gov/vuln/detail/CVE-2022-26912 |
| 418 |
[ 164 ] CVE-2022-29144 |
| 419 |
https://nvd.nist.gov/vuln/detail/CVE-2022-29144 |
| 420 |
[ 165 ] CVE-2022-29146 |
| 421 |
https://nvd.nist.gov/vuln/detail/CVE-2022-29146 |
| 422 |
[ 166 ] CVE-2022-29147 |
| 423 |
https://nvd.nist.gov/vuln/detail/CVE-2022-29147 |
| 424 |
[ 167 ] CVE-2022-30127 |
| 425 |
https://nvd.nist.gov/vuln/detail/CVE-2022-30127 |
| 426 |
[ 168 ] CVE-2022-30128 |
| 427 |
https://nvd.nist.gov/vuln/detail/CVE-2022-30128 |
| 428 |
[ 169 ] CVE-2022-30192 |
| 429 |
https://nvd.nist.gov/vuln/detail/CVE-2022-30192 |
| 430 |
[ 170 ] CVE-2022-33638 |
| 431 |
https://nvd.nist.gov/vuln/detail/CVE-2022-33638 |
| 432 |
[ 171 ] CVE-2022-33639 |
| 433 |
https://nvd.nist.gov/vuln/detail/CVE-2022-33639 |
| 434 |
|
| 435 |
Availability |
| 436 |
============ |
| 437 |
|
| 438 |
This GLSA and any updates to it are available for viewing at |
| 439 |
the Gentoo Security Website: |
| 440 |
|
| 441 |
https://security.gentoo.org/glsa/202208-25 |
| 442 |
|
| 443 |
Concerns? |
| 444 |
========= |
| 445 |
|
| 446 |
Security is a primary focus of Gentoo Linux and ensuring the |
| 447 |
confidentiality and security of our users' machines is of utmost |
| 448 |
importance to us. Any security concerns should be addressed to |
| 449 |
security@g.o or alternatively, you may file a bug at |
| 450 |
https://bugs.gentoo.org. |
| 451 |
|
| 452 |
License |
| 453 |
======= |
| 454 |
|
| 455 |
Copyright 2022 Gentoo Foundation, Inc; referenced text |
| 456 |
belongs to its owner(s). |
| 457 |
|
| 458 |
The contents of this document are licensed under the |
| 459 |
Creative Commons - Attribution / Share Alike license. |
| 460 |
|
| 461 |
https://creativecommons.org/licenses/by-sa/2.5 |
Archives