CVE-2021-21979: High severity bitnami containers vulnerability
In Bitnami Containers, all Laravel container versions prior to: 6.20.0-debian-10-r107 for Laravel 6, 7.30.1-debian-10-r108 for Laravel 7 and 8.5.11-debian-10-r0 for Laravel 8, the file /tmp/app/.env is generated at the time that the docker image bitnami/laravel was built, and the value of APPKEY is fixed under certain conditions. This value is crucial for the security of the application and must be randomly generated per Laravel installation. If your application's encryption key is in the hands of a malicious party, that party could craft cookie values using the encryption key and exploit vulnerabilities inherent to PHP object serialization / unserialization, such as calling arbitrary class methods within your application.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2021-21979?
CVE-2021-21979 has been classified as a moderate severity vulnerability.
How do I fix CVE-2021-21979?
To mitigate CVE-2021-21979, upgrade to Laravel container versions 6.20.0-debian-10-r107, 7.30.1-debian-10-r108, or 8.5.11-debian-10-r0 or later.
What are the affected versions for CVE-2021-21979?
CVE-2021-21979 affects all Laravel container versions prior to 6.20.0, 7.30.1, and 8.5.11.
What impact does CVE-2021-21979 have?
CVE-2021-21979 may allow unauthorized access to sensitive environment variables due to the improper handling of the APP_KEY configuration.
Is there a workaround for CVE-2021-21979?
A potential workaround for CVE-2021-21979 is to manually delete or secure the /tmp/app/.env file in existing container instances.