CVE-2018-3639: Infoleak
An industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of Load & Store instructions (a commonly used performance optimization).
It relies on the presence of a precisely-defined instruction sequence in the privileged code as well as the fact that memory read from address to which a recent memory write has occurred may see an older value and subsequently cause an update into the microprocessor's data cache even for speculatively executed instructions that never actually commit (retire).
As a result, an unprivileged attacker could use this flaw to read privileged memory by conducting targeted cache side-channel attacks.
Other sources
EFI. An information disclosure issue was addressed with a microcode update. This ensures that older data read from recently-written-to addresses cannot be read via a speculative side-channel.
Microcode. An information disclosure issue was addressed with a microcode update. This ensures that older data read from recently-written-to addresses cannot be read via a speculative side-channel.
Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior memory writes are known may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis, aka Speculative Store Bypass (SSB), Variant 4.
Credit
Affected Software
Remediation
Event History
Parent advisories
This vulnerability appears in the following advisories.
- RHSA-2018:2171
- RHSA-2018:2172
- RHSA-2018:1647
- RHSA-2018:1650
- RHSA-2018:1651
- RHSA-2018:1660
- RHSA-2018:1669
- RHSA-2018:1854
- RHSA-2018:2162
- RHSA-2018:2164
- RHSA-2018:1641
- RHSA-2018:1656
- RHSA-2018:1664
- RHSA-2018:2394
- RHSA-2018:3399
- RHSA-2018:3401
- RHSA-2018:1640
- RHSA-2018:1657
- RHSA-2018:1665
- RHSA-2018:3396
- RHSA-2018:3397
- RHSA-2018:1639
- RHSA-2018:1658
- RHSA-2018:1666
- RHSA-2018:2309
- RHSA-2018:3400
- RHSA-2018:3425
- RHSA-2018:1638
- RHSA-2018:1659
- RHSA-2018:1667
- RHSA-2018:1826
- RHSA-2018:2250
- RHSA-2018:3402
- RHSA-2018:3424
- RHSA-2018:1630
- RHSA-2018:2003
- RHSA-2018:1629
- RHSA-2018:1632
- RHSA-2018:1633
- RHSA-2018:1648
- RHSA-2018:1649
- RHSA-2018:1965
- RHSA-2018:1967
- RHSA-2018:1997
- RHSA-2018:2001
- RHSA-2018:2948
- RHSA-2018:1637
- RHSA-2018:1661
- RHSA-2018:1668
- RHSA-2018:2216
- RHSA-2018:3407
- RHSA-2018:3423
- RHSA-2018:1636
- RHSA-2018:1653
- RHSA-2018:1662
- RHSA-2018:1737
- RHSA-2018:2161
- RHSA-2018:3398
- RHSA-2018:1635
- RHSA-2018:1652
- RHSA-2018:1663
- RHSA-2018:1738
- RHSA-2018:2006
- RHSA-2018:2387
- RHSA-2018:1686
- RHSA-2019:0148
- RHSA-2018:1642
- RHSA-2018:2396
- RHSA-2018:1644
- RHSA-2018:2289
- RHSA-2018:1643
- RHSA-2018:2258
- RHSA-2018:2228
- RHSA-2018:1646
- RHSA-2018:2364
- RHSA-2018:1645
- RHSA-2018:2363
- RHSA-2018:1655
- RHSA-2018:1675
- RHSA-2018:1696
- RHSA-2018:2060
- RHSA-2018:1674
- RHSA-2018:1676
- RHSA-2018:2328
- RHSA-2019:1046
- RHSA-2018:1711
- RHSA-2018:2246
- RHSA-2018:1654
- RHSA-2018:1690
- RHSA-2018:1710
- RHSA-2018:1688
- RHSA-2018:1689
- HT209193
- HT209139
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2018-4295
- CVE-2018-4410
- CVE-2018-4417
- CVE-2017-12613
- CVE-2017-12618
- CVE-2018-4411
- CVE-2018-4308
- CVE-2018-4468
- CVE-2018-4126
- CVE-2018-4415
- CVE-2018-4398
- CVE-2018-4412
- CVE-2018-4153
- CVE-2018-4406
- CVE-2018-4346
- CVE-2018-4403
- CVE-2018-4423
- CVE-2018-3639
- CVE-2018-4342
- CVE-2018-4304
- CVE-2018-4426
- CVE-2018-4331
- CVE-2018-3646
- CVE-2018-4242
- CVE-2018-4394
- CVE-2018-4334
- CVE-2018-4396
- CVE-2018-4418
- CVE-2018-4350
- CVE-2018-4421
- CVE-2018-4422
- CVE-2018-4408
- CVE-2018-4402
- CVE-2018-4341
- CVE-2018-4354
- CVE-2018-4401
- CVE-2018-4371
- CVE-2018-4420
- CVE-2018-4399
- CVE-2018-4340
- CVE-2018-4419
- CVE-2018-4425
- CVE-2018-4259
- CVE-2018-4286
- CVE-2018-4287
- CVE-2018-4288
- CVE-2018-4291
- CVE-2018-4413
- CVE-2018-4407
- CVE-2018-4424
- CVE-2018-4187
- CVE-2018-4348
- CVE-2018-4389
- CVE-2018-4326
- CVE-2018-4310
- CVE-2018-3640
- CVE-2018-4369
- CVE-2018-6797
- CVE-2017-0898
- CVE-2017-10784
- CVE-2017-14033
- CVE-2017-14064
- CVE-2017-17405
- CVE-2017-17742
- CVE-2018-6914
- CVE-2018-8777
- CVE-2018-8778
- CVE-2018-8779
- CVE-2018-8780
- CVE-2018-4400
- CVE-2018-4395
- CVE-2018-4393
- CVE-2018-4203
- CVE-2018-4368
- CVE-2018-5383
- CVE-2018-4324
- CVE-2018-4353
- CVE-2018-4321
- CVE-2018-4414
- CVE-2018-4347
- CVE-2018-4333
- CVE-2018-4296
- CVE-2018-4433
- CVE-2019-8643
- CVE-2017-5731
- CVE-2017-5732
- CVE-2017-5733
- CVE-2017-5734
- CVE-2017-5735
- CVE-2018-4332
- CVE-2018-4343
- CVE-2018-4355
- CVE-2018-4351
- CVE-2018-4451
- CVE-2018-4456
- CVE-2018-4383
- CVE-2018-4336
- CVE-2018-4337
- CVE-2018-4344
- CVE-2015-3194
- CVE-2015-5333
- CVE-2015-5334
- CVE-2016-0702
- CVE-2016-1777
- CVE-2018-4338
Frequently Asked Questions
What is the severity of CVE-2018-3639?
CVE-2018-3639 has a severity rating of High due to its potential to allow side-channel attacks through speculative execution.
How do I fix CVE-2018-3639?
To mitigate CVE-2018-3639, apply the latest updates from your operating system vendor that include the necessary microcode updates and kernel patches.
Which software is affected by CVE-2018-3639?
CVE-2018-3639 affects various versions of Windows, Linux kernels, and Intel x86 microprocessors among other platforms and products.
What are the potential impacts of CVE-2018-3639?
The potential impacts of CVE-2018-3639 include unauthorized data access and information leakage through side-channel attacks.
Is there a specific patch version for CVE-2018-3639?
Yes, specific patches for CVE-2018-3639 can be found in updated kernel versions provided by vendors such as Red Hat and Debian.