zenstruck collections up to 0.2.0 EntityRepository::find injection

Summaryinfo

A vulnerability was found in zenstruck collections up to 0.2.0. It has been rated as problematic. Affected by this issue is the function EntityRepository::find. Performing a manipulation results in injection. This vulnerability was named CVE-2023-37473. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in zenstruck collections up to 0.2.0. It has been classified as problematic. This affects the function EntityRepository::find. The manipulation with an unknown input leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

zenstruck/collections is a set of helpers for iterating/paginating/filtering collections. Passing _callable strings_ (ie `system`) caused the function to be executed. This would result in a limited subset of specific user input being executed as if it were code. This issue has been addressed in commit `f4b1c48820` and included in release version 0.2.1. Users are advised to upgrade. Users unable to upgrade should ensure that user input is not passed to either `EntityRepository::find()` or `query()`.

The weakness was presented 07/15/2023 as GHSA-7xr2-8ff7-6fjq. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-37473 since 07/06/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1055 for this issue.

Upgrading to version 0.2.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch f4b1c488206e1b1581b06fcd331686846f13f19c is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• zenstruck

Name

• collections

Version

• 0.1
• 0.2.0

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion