{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21979 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-21979 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-21979 is a high-severity vulnerability in Bitnami Containers, published on 3 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-21979 and fix it if it is affected.\n\nWhat it is: CVE-2021-21979 is a high-severity vulnerability in Bitnami Containers, published on 3 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-21979 in the wild and no public exploit code.\n\nAffected product: Bitnami Containers. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-21979/ (Markdown: https://insights.sbomify.com/CVE-2021-21979/index.md)","id":"CVE-2021-21979","markdown":"https://insights.sbomify.com/CVE-2021-21979/index.md","name":"CVE-2021-21979","record":{"aliases":["GHSA-fqf3-g95f-m2v9"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitnami Laravel container","requires_auth":"none","summary":"Attackers can exploit a hardcoded Laravel APP_KEY in Bitnami containers to craft malicious cookies, potentially leading to remote code execution.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"containers","vendor":"bitnami"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"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 APP_KEY 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in Bitnami Containers","id":"CVE-2021-21979","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in VMware vCenter Server and VMware Cloud Foundation","id":"CVE-2021-21980"},"packages":[],"prev":{"headline":"File upload in VMware View Planner","id":"CVE-2021-21978"},"products":["Bitnami Containers"],"published":"2021-03-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can exploit a hardcoded Laravel APP_KEY in Bitnami containers to craft malicious cookies, potentially leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2021-21979/"}