Improper quoting of columns when calling methods "getByUuid" & "exists" on UUID Model
### Impact The quoting is not done properly in UUID DAO model, so there's the theoretical possibility to inject custom SQL if the developer is using this methods with input data and not doing proper input validation in advance and so relies on the auto-quoting being done by the DAO class. ### Patches Update to version 10.5.19 or apply this patch manually https://github.com/pimcore/pimcore/commit/08e7ba56ae983c3c67ec563b6989b16ef8f35275.patch ### Workarounds Apply https://github.com/pimcore/pimcore/commit/08e7ba56ae983c3c67ec563b6989b16ef8f35275.patch manually. ### References #14633
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-28108US | high7.8 | — | ||
Pimcore is an open source data and experience management platform. Prior to version 10.5.19, quoting is not done properly in UUID DAO model. There is the theoretical possibility to… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/pimcore/pimcorePACKAGE
- https://github.com/pimcore/pimcore/commit/08e7ba56ae983c3c67ec563b6989b16ef8f35275.patchWEB
- https://github.com/pimcore/pimcore/pull/14633WEB
- https://github.com/pimcore/pimcore/security/advisories/GHSA-xc9p-r5qj-8xm9WEB
- https://nvd.nist.gov/vuln/detail/CVE-2023-28108ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan