Heap-double-free vulnerability in systemd
Summary
OSV-2022-475: Heap-double-free in nft_set_context_free_many. Affects systemd versions >= ab51fd9dbdc59f9a37acd8acaea3e9088d092bba, < b48ed70c79c6482e1f39b77d16e62043ff5042a5. Fixed in b48ed70c79c6482e1f39b77d16e62043ff5042a5. 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
systemd is a popular init system and service manager for Linux operating systems. It provides a range of features for managing system processes and services. This vulnerability affects the nft_set_context_free_many function in systemd. The function is responsible for freeing memory in the network filtering subsystem. However, due to a programming error, a double-free condition can occur, leading to a heap-double-free vulnerability.
Vulnerability Detail
The heap-double-free vulnerability in systemd can be triggered when the nft_set_context_free_many function is called. This can result in a crash due to memory corruption. An attacker may be able to exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition. The vulnerability has been assigned a severity rating of HIGH.
How To Fix
Minimum fixed version
b48ed70c79c6482e1f39b77d16e62043ff5042a5
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is recommended to apply the fix provided by the systemd project.
Conclusion
The heap-double-free vulnerability in systemd can lead to memory corruption and potential code execution or denial-of-service. It is crucial to update systemd to a version that includes the fix to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for systemd →
FAQ
This vulnerability can potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition on systems running systemd.
You can use the Vulert playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground and it will analyze it for vulnerabilities.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate the risk.
Yes, this vulnerability can be exploited remotely if the affected system is exposed to the internet and the necessary conditions are met.
The only effective mitigation for this vulnerability is to apply the fix provided by the systemd project.
References
Related vulnerabilities
Recent vulnerabilities recorded for systemd.
