Skip to content

GHSA-9vxv-wpv4-f52p

Information leakage in Error Handler

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-209 Generation of Error Message Containing Sensitive Information
Fix
5.6.10
Upgrade shopware/shopware to this version or later

Description

Impact

Information leakage in Error Handler

Patches

We recommend updating to the current version 5.6.10. You can get the update to 5.6.10 regularly via the Auto-Updater or directly via the download overview.

For older versions you can use the Security Plugin: https://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html

References

https://docs.shopware.com/en/shopware-5-en/security-updates/security-update-05-2021

Affected versions

Packagist

PackageVulnerableFixed in
shopware/shopware
< 5.6.10
5.6.10

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/shopware Packagist → 5.6.10

composer
composer require shopware/shopware:^5.6.10

Weakness

CWE-209: Generation of Error Message Containing Sensitive Information

The product generates an error message that includes sensitive information about its environment, users, or associated data.

How to prevent it
  • Implementation: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files. Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
  • Implementation: Handle exceptions internally and do not display errors containing potentially sensitive information to a user.
  • Implementation: Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
  • Implementation, Build and Compilation: Debugging information should not make its way into a production release.
  • Implementation, Build and Compilation: Debugging information should not make its way into a production release.
  • System Configuration: Where available, configure the environment to use less verbose error messages. For example, in PHP, disable the display_errors setting during configuration, or at runtime using the error_reporting() function.
  • System Configuration: Create default error pages or messages that do not leak any information.

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