{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-16894 exists.","fix":"Apply the vendor's patch.","what":"CVE-2017-16894 is a high-severity vulnerability in n/a, published on 20 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-16894 and fix it if it is affected.\n\nWhat it is: CVE-2017-16894 is a high-severity vulnerability in n/a, published on 20 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-16894 exists.\n\nAffected product: n/a. 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-2017-16894/ (Markdown: https://insights.sbomify.com/CVE-2017-16894/index.md)","id":"CVE-2017-16894","markdown":"https://insights.sbomify.com/CVE-2017-16894/index.md","name":"CVE-2017-16894","record":{"aliases":["GHSA-2v4r-7m2m-5chh"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel framework","requires_auth":"none","summary":"Remote attackers can read sensitive .env file contents, including passwords, due to insecure file permissions in Laravel's key generation command.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"laravel","vendor":"laravel"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In Laravel framework through 5.5.21, remote attackers can obtain sensitive information (such as externally usable passwords) via a direct request for the /.env URI. NOTE: this CVE is only about Laravel framework's writeNewEnvironmentFileWith function in src/Illuminate/Foundation/Console/KeyGenerateCommand.php, which uses file_put_contents without restricting the .env permissions. The .env filename is not used exclusively by Laravel framework.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-08-07","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":1,"refs":[{"date":"2018-08-07","kind":"metasploit","ref":"exploit/unix/http/laravel_token_unserialize_exec","stars":null,"title":"PHP Laravel Framework token Unserialize Remote Command Execution"},{"date":"2019-07-16","kind":"exploitdb","ref":"47129","stars":null,"title":"PHP Laravel Framework 5.5.40 / 5.6.x \u003c 5.6.30 - token Unserialize Remote Command Execution (Metasploit)"},{"date":null,"kind":"nuclei","ref":"http/cves/2017/CVE-2017-16894.yaml","stars":null,"title":"Laravel \u003c5.5.21 - Information Disclosure"}],"tier":"weaponised"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2017-16894","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2017-16895"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2017-16893"},"products":["n/a"],"published":"2017-11-20","related":[{"cvss_score":8.1,"headline":"Laravel Deserialization of Untrusted Data","id":"CVE-2018-15133","kev_date_added":"2024-01-16","published":"2018-08-09"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2021-28254","kev_date_added":null,"published":"2023-04-18"},{"cvss_score":7.5,"headline":"Guard bypass in Eloquent models affecting Laravel illuminate database component","id":"CVE-2020-24940","kev_date_added":null,"published":"2020-09-04"},{"cvss_score":7.5,"headline":"Improper Input Validation in Laravel","id":"CVE-2020-24941","kev_date_added":null,"published":"2020-09-04"},{"cvss_score":7.2,"headline":"Query Binding Exploitation in Laravel","id":"CVE-2021-21263","kev_date_added":null,"published":"2021-01-19"},{"cvss_score":6.1,"headline":"Laravel does not properly constrain the host portion of a password-reset URL","id":"CVE-2017-9303","kev_date_added":null,"published":"2017-05-29"}],"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can read sensitive .env file contents, including passwords, due to insecure file permissions in Laravel's key generation command.","url":"https://insights.sbomify.com/CVE-2017-16894/"}