CVE-2023-0481: Insecure Permissions in RestEasy Reactive implementation of Quarkus
Summary
CVE-2023-0481: RestEasy Reactive implementation of Quarkus allows Creation of Temporary File With Insecure Permissions. Affects io.quarkus.resteasy.reactive:resteasy-reactive-common versions < 3.0.0.Alpha4. Fixed in 3.0.0.Alpha4. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The RestEasy Reactive implementation of Quarkus is a framework that allows developers to build reactive RESTful web services. It is commonly used in Java applications and provides features such as easy integration with other frameworks and efficient handling of HTTP requests and responses. However, a vulnerability has been discovered in the implementation that could lead to the creation of temporary files with insecure permissions.
Vulnerability Detail
The vulnerability arises from the use of the insecure File.createTempFile() method in the FileBodyHandler class of the RestEasy Reactive implementation of Quarkus. This method creates temporary files with insecure permissions, making them readable by local users. An attacker with local access to the system could potentially exploit this vulnerability to gain unauthorized access to sensitive information contained in these temporary files.
How To Fix
Minimum fixed version
3.0.0.Alpha4
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
As a temporary workaround, developers can manually modify the permissions of the temporary files created by the FileBodyHandler class to restrict access to only the necessary users. This can be done using the appropriate file permission settings in the operating system. However, this workaround is not recommended as it requires manual intervention and may not provide complete protection against potential attacks.
Conclusion
In conclusion, the RestEasy Reactive implementation of Quarkus is vulnerable to the creation of temporary files with insecure permissions. This could allow local users to read sensitive information. It is recommended to update the affected package to version 3.0.0.Alpha4 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for io.quarkus.resteasy.reactive:resteasy-reactive-common →
FAQ
The vulnerability allows local users to read sensitive information contained in temporary files created by the RestEasy Reactive implementation of Quarkus. However, it does not directly enable remote code execution or privilege escalation.
No, only versions prior to 3.0.0.Alpha4 of the io.quarkus.resteasy.reactive:resteasy-reactive-common-parent package are affected by this vulnerability.
There are no known public exploits for this vulnerability at the time of this advisory. However, it is still important to apply the recommended fix to mitigate the risk of potential attacks.
No, this vulnerability requires local access to the system in order to exploit it. Remote exploitation is not possible.
If possible, developers can consider using alternative libraries or frameworks that do not have this vulnerability. However, it is important to thoroughly evaluate the security of any alternative solution before making a switch.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
