Read Out-of-Bound Vulnerability in crypto: arm64/poly1305
Summary
GSD-2022-1005701: crypto: arm64/poly1305 - fix a read out-of-bound. Affects Kernel versions >= f569ca16475155013525686d0f73bc379c67e635, < 3d4c28475ee352c440b83484b72b1320ff76364a. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The crypto: arm64/poly1305 package is a cryptographic library used in the Linux Kernel. It provides the Poly1305 message authentication code, which is used for data integrity and authenticity verification. The vulnerability in this package allows for a read out-of-bound, potentially leading to information disclosure or other security issues.
Vulnerability Detail
The vulnerability in crypto: arm64/poly1305 arises from a read out-of-bound error. This means that the code attempts to read data from memory beyond the bounds of what is allocated, potentially accessing sensitive information or causing a crash. The impact and attack plausibility of this vulnerability have not been proven yet. It was introduced in version v5.5 of the Linux Kernel and fixed in version v5.15.60 by commit 3d4c28475ee352c440b83484b72b1320ff76364a.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability.
Conclusion
The read out-of-bound vulnerability in crypto: arm64/poly1305 can potentially lead to information disclosure or other security issues. It is recommended to update the Linux Kernel to version v5.15.60 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially lead to information disclosure or other security issues.
You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will alert you in real-time if any open-source vulnerabilities, including this one, are found.
Yes, a fix for this vulnerability is available in version v5.15.60 of the Linux Kernel. It is recommended to update to this version or later.
No specific workaround has been mentioned for this vulnerability. It is recommended to update to the fixed version of the Linux Kernel.
You can find more information about this vulnerability in the GSD-2022-1005701 entry of the GSD database: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1005xxx/GSD-2022-1005701.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
