# CVE-2017-16894: Information disclosure in n/a

> Remote attackers can read sensitive .env file contents, including passwords, due to insecure file permissions in Laravel's key generation command.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2v4r-7m2m-5chh

## What is CVE-2017-16894?

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.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-16894?

It affects 1 product.


Products: Laravel Laravel.

## How do I fix CVE-2017-16894?

Apply the vendor's patch.

## Is CVE-2017-16894 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-16894 exists.

Public exploit code:

- PHP Laravel Framework token Unserialize Remote Command Execution (metasploit)
- PHP Laravel Framework 5.5.40 / 5.6.x < 5.6.30 - token Unserialize Remote Command Execution (Metasploit) (exploitdb)
- Laravel <5.5.21 - Information Disclosure (nuclei): http/cves/2017/CVE-2017-16894.yaml

## Other vulnerabilities in n/a

- [CVE-2018-15133](https://insights.sbomify.com/CVE-2018-15133/): Laravel Deserialization of Untrusted Data (high 8.1, exploited in the wild)
- [CVE-2021-28254](https://insights.sbomify.com/CVE-2021-28254/): Deserialization in n/a (critical 9.8)
- [CVE-2020-24940](https://insights.sbomify.com/CVE-2020-24940/): Guard bypass in Eloquent models affecting Laravel illuminate database component (high 7.5)
- [CVE-2020-24941](https://insights.sbomify.com/CVE-2020-24941/): Improper Input Validation in Laravel (high 7.5)
- [CVE-2021-21263](https://insights.sbomify.com/CVE-2021-21263/): Query Binding Exploitation in Laravel (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-16894 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-16894 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-16894/ (Markdown: https://insights.sbomify.com/CVE-2017-16894/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-16894
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-16894
- OSV: https://osv.dev/vulnerability/CVE-2017-16894

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-16894/
Summaries are generated and may contain mistakes; the official description above is the record.