CVE-2019-1125 Affecting kernel-debuginfo package, versions <0:4.14.133-113.112.amzn2
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-AMZN2-KERNELDEBUGINFO-1671894
- published 27 Sep 2021
- disclosed 3 Sep 2019
Introduced: 3 Sep 2019
CVE-2019-1125 Open this link in a new tabHow to fix?
Upgrade Amazon-Linux:2
kernel-debuginfo
to version 0:4.14.133-113.112.amzn2 or higher.
This issue was patched in ALAS2-2019-1253
.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-debuginfo
package and not the kernel-debuginfo
package as distributed by Amazon-Linux
.
See How to fix?
for Amazon-Linux:2
relevant fixed versions and status.
An information disclosure vulnerability exists when certain central processing units (CPU) speculatively access memory. An attacker who successfully exploited the vulnerability could read privileged data across trust boundaries. To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted application. The vulnerability would not allow an attacker to elevate user rights directly, but it could be used to obtain information that could be used to try to compromise the affected system further. On January 3, 2018, Microsoft released an advisory and security updates related to a newly-discovered class of hardware vulnerabilities (known as Spectre) involving speculative execution side channels that affect AMD, ARM, and Intel CPUs to varying degrees. This vulnerability, released on August 6, 2019, is a variant of the Spectre Variant 1 speculative execution side channel vulnerability and has been assigned CVE-2019-1125. Microsoft released a security update on July 9, 2019 that addresses the vulnerability through a software change that mitigates how the CPU speculatively accesses memory. Note that this vulnerability does not require a microcode update from your device OEM.
References
- https://kc.mcafee.com/corporate/index?page=content&id=SB10297
- https://www.synology.com/security/advisory/Synology_SA_19_32
- http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20200408-01-swapgs-en
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1125
- http://packetstormsecurity.com/files/156337/SWAPGS-Attack-Proof-Of-Concept.html
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1125
- https://access.redhat.com/errata/RHBA-2019:2824
- https://access.redhat.com/errata/RHBA-2019:3248
- https://access.redhat.com/errata/RHSA-2019:2600
- https://access.redhat.com/errata/RHSA-2019:2609
- https://access.redhat.com/errata/RHSA-2019:2695
- https://access.redhat.com/errata/RHSA-2019:2696
- https://access.redhat.com/errata/RHSA-2019:2730
- https://access.redhat.com/errata/RHSA-2019:2899
- https://access.redhat.com/errata/RHSA-2019:2900
- https://access.redhat.com/errata/RHSA-2019:2975
- https://access.redhat.com/errata/RHSA-2019:3011
- https://access.redhat.com/errata/RHSA-2019:3220
- https://www.exploit-db.com/exploits/48071