GHSA-3pcr-4982-548m json
Exposure of .env if project root is configured as web root in shopware/production
published 5y ago modified 2mo ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Impact
The .env and other sensitive files can be leaked if the project root and not `/public` is configured as the web root.
### Patches We recommend to update to the current version 6.3.5.3. You can get the update to 6.3.5.3 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
### Workarounds
You should always use `/public` as the web root.
For older versions of 6.1 and 6.2, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659
### For more information https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-04-2021
Patch / fix
- packagist shopware/production 6.3.5.3
- packagist shopware/shopware 6.3.5.3
Is GHSA-3pcr-4982-548m in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | shopware/production | <6.3.5.3 |
6.3.5.3 |
| packagist | shopware/shopware | <6.3.5.3 |
6.3.5.3 |
Classification
- Weakness
-
- CWE-552 Files or Directories Accessible to External Parties
References
Sources
- GitHub Advisory GHSA-3pcr-4982-548m
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.