Skip to content

GHSA-3pcr-4982-548m

Exposure of .env if project root is configured as web root in shopware/production

Medium Packagist
Severity
Medium
The publisher's own rating, not a CVSS score
Exploit chance (EPSS)
—
No score published
Known exploited
No
Not in CISA's catalog
Weakness
CWE-552 Files or Directories Accessible to External Parties
Fix
Available
2 packages have a fixed version

Description

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

Affected versions

Packagist

PackageVulnerableFixed in
shopware/production
< 6.3.5.3
6.3.5.3
shopware/shopware
< 6.3.5.3
6.3.5.3

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

shopware/production Packagist → 6.3.5.3

composer
composer require shopware/production:^6.3.5.3

shopware/shopware Packagist → 6.3.5.3

composer
composer require shopware/shopware:^6.3.5.3

Weakness

CWE-552: Files or Directories Accessible to External Parties

The product makes files or directories accessible to unauthorized actors, even though they should not be.

How to prevent it
  • Implementation, System Configuration, Operation: When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.

References

Timeline

  1. Published
  2. Last updated by the source
AdvisorySeverityWhy it's related
GHSA-7cw6-7h3h-v8pf
Shopware Has Improper Control of Generation of Code in Twig rendered views
High Also affects shopware/shopware
GHSA-6w82-v552-wjw2
Shopware Storefront Reflected XSS in Storefront Login Page
Medium Also affects shopware/shopware
GHSA-9v82-vcjx-m76j
Shopware: Reflective Cross Site-Scripting (XSS) in CMS components
High Also affects shopware/shopware
GHSA-83jv-4prm-34g7
Shopware Remote Code Execution Vulnerability
Critical Also affects shopware/shopware
GHSA-7336-ghhp-f2qj
Shopware Remote Code Execution Vulnerability
Critical Also affects shopware/shopware
GHSA-jqr7-5h7r-ch8p
Shopware Non-Persistent XSS in the Frontend
Medium Also affects shopware/shopware
GHSA-q3g4-2vw9-xv27
Shopware Remote Code Execution Vulnerability
Critical Also affects shopware/shopware
GHSA-gh66-fp7j-98v5
Shopware improper mail validation vulnerability
Medium Also affects shopware/shopware
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor